Hi Fernand,
oStatement.setNull(1, ) for a textfield works fine ( =
long
SQLType others)
oStatement.setNull(2, ) for a timestamp returns 00-00-00
00:00:00 and not the Mysql (null)
i tried SQLtype 0 also with same results
Is this not a bug in that version (which one,
Alex Thurgood wrote:
Is this not a bug in that version (which one, by the way) of the ODBC driver ?
I have had this problem for a long time, and it has caused me no end of
trouble, for example when I switched to the JDBC driver and it couldn't handle
default -00-00 strings. It occurs on
Hi Fernand,
did you query for the type of the column?
resultSet.columns.getByName(myCol).Type?
oStatement.setNull(1, ) for a textfield works fine ( = long
SQLType others)
oStatement.setNull(2, ) for a timestamp returns 00-00-00
00:00:00 and not the Mysql (null)
i tried SQLtype 0
Peter,
stupid me, my rowset is client site
but the server site resultset gives also 93 as type
?
Peter ,
Thanks for the hint but no luick , the type in the rowset = 93 this
gives and still a lot of 0's and no (null) in my table
as i use a SQL statement i do not alter the rowset but
