>> which suggests that referring to rowids is fine. > > It does not suggest referring to ROWIDs is fine, it only says that it > can be done. I think Pavel's point is that referencing ROWIDs is bad > practice, so that is why he says you shouldn't do it.
Yes, that's right. You can refer to rowid, but it's a bad practice. Especially if you refer to it in foreign keys. As you have seen just vacuum the database and suddenly you see some bugs, incorrect foreign key references and you don't understand how they were able to make their way into the database. You are right that by just adding a column ROWID INTEGER PRIMARY KEY you can fix things without changing much of the code but it would be a big confusion for any developer who will look at your code either after you or as an additional developer on the project. So in a short term if you want a quick hack that would be fairly decent solution. But in a long term I would suggest to add column ID INTEGER PRIMARY KEY and change all references to rowid towards id. Pavel On Thu, Apr 28, 2011 at 9:31 PM, Rich Rattanni <ratta...@gmail.com> wrote: >> "You can access the ROWID of an SQLite table using one the special column >> names ROWID, _ROWID_, or OID. Except if you declare an ordinary table column >> to use one of those special names, then the use of that name will refer to >> the declared column not to the internal ROWID." >> >> which suggests that referring to rowids is fine. > > It does not suggest referring to ROWIDs is fine, it only says that it > can be done. I think Pavel's point is that referencing ROWIDs is bad > practice, so that is why he says you shouldn't do it. > > -- > Rich > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
