Home/ Questions/Q 616417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T18:19:30+00:00

I’m using SubSonic 2.2 and sqlite and have encountered a problem when dealing with

  • 0

I’m using SubSonic 2.2 and sqlite and have encountered a problem when dealing with tables with an INTEGER PRIMARY KEY column that isn’t AUTOINCREMENT. According to the faq:

If you declare a column of a table to be INTEGER PRIMARY KEY, then whenever you insert a NULL into that column of the table, the NULL is automatically converted into an integer which is one greater than the largest value of that column over all other rows in the table, or 1 if the table is empty.

So sqlite thinks these columns are sometimes auto incremented (ie just when NULL values are provided). The problem is that SubSonic thinks they are always auto incremented.

In my application my ID values are generated from a remote database, so I don’t want to auto-generate them in sqlite. This should be no problem: I’ll simply provide values when I create records in this table. However, when I use SubSonic’s sonic.exe to auto-generate my DAL, the primary key column is set to AutoIncrement = true. This seems to mean that I can’t set the ID column – subsonic’s ActiveHelper.GetInsertCommand() ignores it, since it thinks it’s auto-generated.

The line where it determines whether it’s autoincrement or not is in SubSonic.SQLiteDataProvider.GetTableSchema():

column.AutoIncrement = Convert.ToBoolean(row["PRIMARY_KEY"]) && GetDbType(row["DATA_TYPE"].ToString()) == DbType.Int64;

I guess the solution is either to

  • Not use INTEGER PRIMARY KEY columns for keys that are generated elsewhere, or

  • Modify the templates so these sorts of columns are not set to AutoIncrement = true. This would mean SubSonic won’t ever treat them as auto increment, so I’d need to be careful that I don’t later expect to get auto generated values. Unfortunately I don’t think it’s possible within the templates to easily determine if the column really is AUTOINCREMENT or not, so maybe I’d have to do some ugly hard-coding instead….

Any other thoughts or suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Unfortunately it looks like our SQLiteDataProvider assumes that if it’s an Int64 PK, then it’s auto-increment. I’m looking over the source right now (I didn’t write this provider) and I can see that the way the schema is being loaded is using Connection.GetSchema – which uses built System.Data.Common.DbConnection to get the schema for the tables.

    This is suboptimal most of the time because it returns limited information. In this case – it’s not telling us if the column is AUTOINCREMENT or not. There’s probably a better way to ask SQLite the meta information on the table – but it wasn’t used unfortunately.

    Short answer: define a new PK, if you can, and use the other key as a reference.

    • 0