On 11/7/06, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
In general, there is no rowid associated with a row returned by select. A row may be constructed out of data taken from multiple rows of multiple tables, or be manufactured without reference to any table at all. If you want a rowid from a particular table, why not just retrieve it explicitly, as a column in select statement?
That works fine if you control all the SQL. But if you are the author of a wrapper, and your users are going to be creating all the SQL, then you have to do tricks to get the rowid for any records in query results. Or, you have to require users to add 'rowid' to all of their queries. Without the rowid, it makes it impossible to provide a high-level API for editing records. Obviously, there are an infinite number of queries for which a rowid doesn't exist. For those queries, a sqlite3_rowid call should just return an error. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
