Hi,

> I've understand the matter. But I think that the driver can parse
> the statement to change the = ? in is null when i set a value with setNull

No, it shouldn't. Parsing and changing the statement defeats the
purpose of the PREPAREDStatement - when you change the
statement, you need to re-prepare it ... This will clear current
parameter bindings.

> It's true that the jdbc specification it's clear but It's a logical think
> execute this parsing in where condition case.

> In this case the PreapredStatement is useless if you have any possibility
> to have a null value in where condition (for select, update, delete)

You're the programmer - you should know when to use a prepared
statement and when not to. In this case, if your SQL is totally
dynamic, tell me: what is the use of a PreparedStatement??

Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."