While implementing a table that intended for arbitrary table storage, I
automatically named some field rowid not linking at the moment that it will
have a name conflict with sqlite internal rowid name. Lately I discovered
this, and (not a big deal) recreated table with a different name. But just
While implementing a table that intended for arbitrary table storage, I
automatically named some field rowid not linking at the moment that it
will
have a name conflict with sqlite internal rowid name. Lately I discovered
this, and (not a big deal) recreated table with a different name. But
On Wed, May 26, 2010 at 6:19 PM, Pavel Ivanov paiva...@gmail.com wrote:
But just
wondering, was allowing to create such field intentional? As I suppose
such
field is complete phantom since most sql queries will interpret rowid
internally and won't allow access this user field at all.