On Wed, Jan 21, 2004 at 03:22:29AM -0500, jim wrote: > for some reason they are trying to name the constraint. no idea why.
That determines the name of the index that will be used to implement the constraint. > It appears sqlitemanager doesn't use it. Yup, it looks like sqlite ignores the constraint name and just gives the index an autogenerated name: sqlite> create table foo (name text constraint name_dx primary key); sqlite> .indices foo (foo autoindex 1) whereas Postgres does use the name classical=# create table foo (name text constraint name_dx primary key); NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'name_dx' for table 'foo' CREATE TABLE > from this day forth constraints will have no name. Well, they do have a name, you just can't give them your own name AFAIK. Dave Cook --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
