I've just hunted down a problem with jdbcPreparedStatement.setObject(int, Object):
I have a select statement that tries to select all rows that have a certain column match a parameter ( "select * from a where blah=?" ) and the passed in parameter gets converted into a null before the query is executed. The reason for this is the fact that the Parser constructs a parameter Expression that has Types.NULL as the type and setObject now uses that type information to convert the object into the widest possible data type that matches the expected type.
I am unsure which of the parts is the bug:
- either the parser should find the type information for the referenced column on the other side of the comparison
- or the converter should never try to convert something to Types.NULL because that is used as a placeholder for "unknown type"
What is the plan? I could try to patch it if I knew what the master plan is.
Harald
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
