Hi Alain, Mariano > Yes, that is what is expected, but in the case of SQLite, the column > type changes to SQLITE_NULL for nulls and that is a problem in > squeakdbx now. I think column datatype should not be stored in the > resultset in the case of sqlite. Other databases don't behave this > way (as far as I can remember), so, overriding moveNext for sqlite > would probably be fine.
SQLite introduces a new data type SQLITE_NULL and unfortunately, the column type changes if NULL values occur - independent of what the real data type of the column is. In all other database libraries, this isn't the case. Norbert ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ libopendbx-devel mailing list libopendbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopendbx-devel http://www.linuxnetworks.de/doc/index.php/OpenDBX
