"Paskamp, Marco" wrote:
hello!
> > PreparedStatement.clearParameters() don't work.
any news on this bug?
> > PreparedStatement.executeQuery() if the
> > preparedStatement has parameters and was not set must throw
> > SQLException.
>
> I`m not sure if the JDBC-specification defines to throw an exception if a
> parameters was not set. At the moment the driver initialize these parameters
> as null values. Should I change this behaviour and throw an exception? Hints
> are welcome.
i find it very comfortable that the driver uses NULL values. at also
make sense in SQL-think, IMHO. i use this feature, so my vote is for
keeping it the way it is. however, if it clearly violates the JDBC spec
if would be ok to be changed. if the JDBC spec is not clear about it,
leave it as it is now.
just my 0.02 EUR,
Raimund
--
Raimund Jacob
\|/ ____ \|/
Pinuts Media+Science GmbH "@'/ ,. \`@"
Potsdamer Str. 96 /_| \__/ |_\
D-10785 Berlin \__U_/
http://www.pinuts.de/ voice: +49 30 590090313 fax: +49 30 590090390
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
