I'm trying to track down whose code is responsible for this problem. Your example (and I suppose sqlalchemy) use an sqlite3 module, which seems to only exist within the python source tree. upgrading pysqlite from initd.org gives me a pysqlite2 module. (Using the pysqlite2.dbapi2 module does not seem to carry the same error.)
So the bug seems present only in the python 2.5 sqlite3 module. What next? ~jon On Feb 15, 10:14 am, Michael Schlenker <[EMAIL PROTECTED]> wrote: > Michael Bayer schrieb:> no idea. below is a revised version, where the main > revision is that > > theres no SQLAlchemy ;). So I think you should submit this to the bug > > tracker onwww.sqlite.org. > > > Actually this is sorta interesting since it would impact our own unit > > tests regarding sqlite as well (which is why we run them with mysql > > and postgres as part of our build as well). > > This is a known misfeature of sqlite..., its even documented in the CREATE > TABLE manpage for sqlite. > > Michael > > -- > Michael Schlenker > Software Engineer > > CONTACT Software GmbH Tel.: +49 (421) 20153-80 > Wiener Straße 1-3 Fax: +49 (421) 20153-41 > 28359 Bremenhttp://www.contact.de/ E-Mail: [EMAIL PROTECTED] > > Sitz der Gesellschaft: Bremen > Geschäftsführer: Karl Heinz Zachries, Ralf Holtgrefe > Eingetragen im Handelsregister des Amtsgerichts Bremen unter HRB 13215 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
