Markus Hoenicka <markus.hoeni...@mhoenicka.de> wrote: > I doubt that allowing BIGINT to auto-increment is the proper solution > of the underlying problem. I'd like to focus your attention again on > the example of the OP: > > sqlite> CREATE TABLE test(id INTEGER PRIMARY KEY, int INTEGER, bigint > BIGINT); > sqlite> PRAGMA table_info(test); > 0|id|INTEGER|0||1 > 1|int|INTEGER|0||0 > 2|bigint|BIGINT|0||0 > > We've heard in this discussion repeatedly that all integers are > created equal (as far as SQLite is concerned), and that applications > using SQLite should keep track of the data types themselves if size > matters. However, as Richard points out, INTEGER PRIMARY KEY is > different from INTEGER and from anything else. All I need as an > application (or abstraction layer FWIW) author therefore is that > SQLite tells me that that particular column is different.
Well, you get that 1 in the last column, indicating the column is in fact part of a primary key. So, if it's INTEGER, and it's the only column marked PRIMARY KEY, then it's the special one. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
