One additional thing not listed in this document -- use of a internal
rowid alias (OID, ROWID or _ROWID_) will produce a parse error on a
query against a WITHOUT ROWID table (unless, of course, it has an actual
column with the specified name), which makes sense, of course, but
could be an issue for generic table handling code that currently uses
any of those.
The fact that the presence of such a table makes a database containing
one unreadable at releases before 3.8.2 is a bit of an issue for those
using SQLite as a data exchange format (like GeoPackages), but then
that's true with partial indexes too.
Peter
On 11/15/2013 4:47 AM, Luís Simão wrote:
SQLite answers those question in:
http://www.sqlite.org/draft/withoutrowid.html
BR
_______________________________________________
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
