RE: [sqlite] Re: auto_increment - why does it do the opposite?

2007-08-09 Thread Griggs, Donald
Regarding: " This works, probably because sqlite doesn't enforce column types..." Yes, you can create table ABC ( myCol WARM_AND_FUZZY); And this will be parsed without error. - To unsubscribe, send email to

Re: [sqlite] Re: auto_increment - why does it do the opposite?

2007-08-09 Thread Paul Harris
ok... That explains how autoincrement works, but it doesn't explain why the AUTO_INCREMENT keyword made it through the parser without raising an error or doing what I would expect - and work as an AUTOINCREMENT table. perhaps, it is the same reason this works: sqlite> create table abc (id not

Re: [sqlite] Re: auto_increment - why does it do the opposite?

2007-08-09 Thread miguel manese
Igor has answered this before. Roughly: 1. all tables has an implicit integer column named "rowid" that is auto increment 2. creating an integer primary key effectively "renames" rowid to that column, so in your case below fields id and rowid are the same IIRC drh replied something else, and

[sqlite] Re: auto_increment - why does it do the opposite?

2007-08-09 Thread Paul Harris
On 09/08/07, Paul Harris <[EMAIL PROTECTED]> wrote: > Hi, > > Can someone please explain why adding the auto_increment term seems to > STOP the auto_increment behaviour? > > $ sqlite3 > SQLite version 3.3.17 > Enter ".help" for instructions > sqlite> .headers on > sqlite> create table abc (id