Hello everybody,
Mea culpa: it was all my fault, not SQLite's.
After a few hours debugging, I'm happy to report that I've found and fixed the bug which was found in QuickLite. The culprit was datatypesForTable, which returned a dictionary. That silly mistake caused the order to be totally messed up. I tables with very few columns, so it's likely that even though the columns were reordered, I never saw that elsewhere because the "random" order matched the orifinal one. As I said, it's been fixed and I will release the new version in the next days.
On Nov 20, 2004, at 02:36, D. Richard Hipp wrote:
To be honest, I'm not sure the test suite checks the case where you explicitly declare ROWID INTEGER PRIMARY KEY. But I did just try this myself and I cannot seem to reproduce the problem. Can anybody else get it to fail?
I explicitly declare ROWID INTEGER PRIMARY KEY and works fine. I'm pretty much sure the error was 100% located on my side.
Thanks everybody for your help and quick response.
Best regards,
-- Tito
