Insert function assumes primary key is auto increment

[xo]

Insert function assumes primary key is auto increment

[kenshaw]

Yes; I would suggest creating custom templates using the base templates then. I am working on a general solution for this, but it is not yet ready to be released, as it requires a lot of rejigging of the templates.

[yurisklar]

Is this issue going to be addressed any time soon? Or would you accept some help with the implementation?

[stevenh]

A related issue we have is it assumes a primary key is a single field which is not necessarily the case.

[kenshaw]

Yes, for reference I would appreciate any pull requests. We don't make any use of SQLite at my company, so I'm not likely to ever get around to fixing this. I'm more than willing to help with / give advice on / test any pull request.

[turnkey-commerce]

I think for SQLite we can do an additional query to determine if it's autoincrement, see this SO answer: http://stackoverflow.com/questions/20979239/how-to-tell-if-a-sqlite-column-is-autoincrement. I'll take a look at implementing this as the problem was apparent on the SQLite DB I was testing,.

[turnkey-commerce]

Am working on this but found that for new databases, for example the Django example, the sqlite_sequence table is not reliably populated until all tables have data. Working on an alternate method to query for the SQL and check for the AUTOINCREMENT keyword for the table.

[turnkey-commerce]

Ken, this is resolved can you please close it?