On Fri, Nov 15, 2013 at 4:11 PM, RSmith <rsm...@rsweb.co.za> wrote:
> I would still like to see some kind of function, even a totally new one
> that does not affect any backward compatibility, such as:
>
> *BOOL sqlite3_table_has_rowid(*tbl);
>
> where maybe if the 'tbl' parameter is empty it checks all tables and lets
> us know whether any tables in the Schema does not contain a rowid (FALSE)
> etc.
>
Here's a thought: What does your hypothetical function return for a table
defined as follows:
CREATE TABLE strange(rowid TEXT, _rowid_ TEXT, oid TEXT);
That table has a rowid, but it is completely inaccessible to the
application. Does your function return TRUE or FALSE?
My point: I think any application that depends on there being a column
named "rowid" that is the key to the table is already broken. WITHOUT
ROWID does not add any new brokenness.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
