> > According to Igor all that happens when you create a primary > > key is that an index with the unique constraint is created. And > > the only good reason for not being able to drop it, as far as I > > can tell, is so that the SQL statement stored for the table is not > > made invalid. > > Yes, however, if you do define a PRIMARY KEY then that internal > index is used instead of the ROWID, hence, you can't delete that > because it would violate what you told the db to do otherwise.
Ah, OK. So there is an internal implication of PRIMARY KEY vs a UNIQUE index. Thanks. Hugh _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
