> I can't understand why is it a bad practice to use database-provided features?
You can use it when you are selecting. And even in this case you should use caution because without explicit column declared by you SQLite can change rowids without notice. And for foreign keys it's mandatory to reference to real columns. > I think this is a bug. It should be fixed. Nope, it's not a bug. > I just wanted to write less text in my queries. Where does explicitly declared column containing rowid introduce more text to your queries? Could you give us examples? I bet in all of them either you don't understand something or you use non-reliable techniques which should be ditched at some point anyway if you want to write easily readable and supportable application. Pavel On Mon, Aug 23, 2010 at 9:50 AM, inst <i...@mail.ua> wrote: >> Make it your rule of thumb: don't ever use rowid, declare your own >> column as "integer primary key" and use it. It will come at no cost >> for you and everything else will work much better. > > I just wanted to write less text in my queries. > I can't understand why is it a bad practice to use database-provided features? > > I think this is a bug. It should be fixed. > _______________________________________________ > 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
