Recent changes to feature-requests

Specify parameters in Java

2009-02-18T13:02:55Z

It would be nice to give people the choice of either using XML or using Java code to specify the procedure parameters

Sure, it's good to provide the parameters in XML for people to not have to use Java, but when writing the JUnit test cases in Java anyway, I'd rather not have to learn the XML tags, but specify them as some sort of criteria object instead

STRUCT as input parameter

2009-02-18T12:57:42Z

SQLUnit currently allows for STRUCT types to be returned from the stored procedure, but doesn't allow them to be specified as the input parameter

This would be really useful as we have large packages, containing various procedures, that take STRUCT types as their parameters (and return STRUCT types)

Named Parameters in XML file

2005-08-15T15:33:50Z

SQLUnit should support calling stored procedures using
named parameters in the XML test file.

This can be very useful when a stored procedure has
say 10 parameters but only 2 are mandatory.

It also aids maintenance, as when stored procedures
get updated we usually make the extra parameters
optional (default their values).

Ant properties as variables in sqlunit test file

2005-03-14T13:12:20Z

Hi,

i would be nice if we could set properties in the Ant
script and use them in the SQLUnit test file, like this:

Ant script:

<property name="db.local.url"
value="jdbc:oracle:thin:@127.0.0.1:1556:TEST" />
<property name="db.local.user1"
value="che />
<property name="db.local.pass1"
value="che" />

SQLUnit test file:

<driver>oracle.jdbc.driver.OracleDriver</driver
>
<url>${db.local.url}</url>
<user>${db.local.user1}</user>
<password>${db.local.pass2}
</password>
</connection>

Bye
Che

store procedure does not work inside sql file.

2004-10-05T17:36:44Z

Hi ,

After fixing above bug 1032804 in 4.1, stored procedure
inside sql file does not work. This is happening because
store procedure needed to be treated specially for
delimiter
consideration.

Thanks,
Satish

create procedure Web_schm_proc as
begin
insert into SPSS_RDM_D_SCHEMA_VERSION Values
(S_RDM_D_SCHEMA_ID.NextVal, 'Web', '0.00.000.190',
null,
SYSDATE, SYSDATE);
end;
/

Set tag should allow embedded SQL to set variables

2004-08-19T02:15:08Z

The set tag currently looks like this:
<set name="name" value="value" />
it should accept setting values from variables using
embedded SQL, something like this:
<set name="query">
..<sql><stmt>select col1, col2 from tab1 where
condition</stmt></sql>
..<resutl>
....<resultset id="1">
......<row id="1">
........<col id="1" name="col1"
type="INTEGER">${col11}</col>
........<col id="2" name="col2"
type="VARCHAR">${col21}</col>
......</row>
......</row id="2">
........<col id="1" name="col1"
type="INTEGER">${col12}</col>
........<col id="2" name="col2"
type="VARCHAR">${col22}</col>
......</row>
....</resutlset>
..</result>
</set>

which would set ${col11}, ${col12}, ${col21} and ${col22{.

SQLUnit does not guarantee result ordering

2004-08-19T02:10:19Z

SQLUnit needs to support the case where the resultset
is ordered differently from a stored procedure or SQL
call from what is specified as the result.

We are looking at using a @sort-by attribute in the
resultset tag in the result element. When the test tag
encounters this, it will sort the corresponding
resultset elements before comparing.