As discussed in trac ticket #1016, we would need to add support to Column such that **kwargs with dialect names are parsed, such as sqlite_autoincrement=True. The ticket has been accepted and just needs someone to contribute a patch. We definitely are not going to link the existing "autoincrement" flag to SQLite's AUTOINCREMENT keyword - its a very rarely used keyword in SQLite and as their documentation states that it causes a degrade in performance - SQLite primary key columns are "autoincrementing" in the general sense in any case, at least as far as that they generate primary key values automatically.
The purpose of the existing "autoincrement" is documented, and is only provided to "turn off" automatic-generate-primary-key behavior for databases which have an option in this regard, which does not include SQLite. On Nov 13, 2008, at 4:16 AM, Sok Ann Yap wrote: > > SQLAlchemy doesn't seem to generate "INTEGER PRIMARY KEY > AUTOINCREMENT" column in sqlite, even though the Column has > autoincrement=True. According to sqlite website[1], if the > AUTOINCREMENT keyword is set, it will use an actual sequence, > otherwise it will just grab the largest id + 1. The later behavior > caused one of our unit test to fail, and due to our unfamiliarity with > SA/sqlite, we spent hours to uncover the cause of the problem. It will > be great if SA can set the AUTOINCREMENT keyword in sqlite if the > autoincrement argument is set to True. > > Regards, > Yap > > [1] http://www.sqlite.org/autoinc.html > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
