Quoting Kris Groves <[EMAIL PROTECTED]>: > Hi, > > I've detected a problem with the code I wrote here. > Normally sqlite3, when returning a result column in the format > tablename.columnname, the real table name is returned, regardless if it was > aliased in the original sql statement. > I've just discovered that if you do a 'select distinct' sqlite3 returns the > tablename alias, and as a result fails to resolve the field type for that > column.
Is this problem so severe that we should revert the driver to the previous version until a fix is available? Or do you think you can fix this problem in a matter of days? regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
