Re: [sqlite] SQLITE return codes for insert/delete/update/select

On 5/11/2011 3:52 PM, cricketfan wrote: > > I dont know if it is just me but I find the return codes for SQL operation > quite confusing. I am new to SQLITE, have learnt a few things and wanted to > know if going in the correct direction, You are thinking in the wrong direction. SQLITE_DONE means

Re: [sqlite] SQLITE return codes for insert/delete/update/select

>I agree with what you stated but it would have been more clearer if >the result of the update statement was a "RECORD NOT FOUND" return >value since it did not find any that met the query's criteria. How can >you say that the UPDATE was successful when the record you were >looking for does

Re: [sqlite] SQLITE return codes for insert/delete/update/select

On Wed, May 11, 2011 at 10:27 PM, Igor Tandetnik wrote: > See also: http://en.wikipedia.org/wiki/Vacuous_truth > Thanks for that - that's a new term for me. i think the relevant bit of that article in this context is: -- Thus we say S is vacuously true; it is true, but

Re: [sqlite] SQLITE return codes for insert/delete/update/select

On 5/11/2011 4:21 PM, cricketfan wrote: > How can you say that the UPDATE was successful when the > record you were looking for does not even exist in the DB? Your statement says: update all records that meet condition X. SQLite did exactly that. How is this not a success? A failure would be if

Re: [sqlite] SQLITE return codes for insert/delete/update/select

oking for does not even exist in the DB? -- View this message in context: http://old.nabble.com/SQLITE-return-codes-for-insert-delete-update-select-tp31597492p31597723.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SQLITE return codes for insert/delete/update/select

On 5/11/2011 3:52 PM, cricketfan wrote: > 1. Return code for an UPDATE/DELETE query (ignoring other error conditions) > will be SQLITE_DONE regardless of the fact whether UPDATE succeeded or > failed. The only way to know whether the UPDATE succeeded or not is to use > sqlite3_changes() to

[sqlite] SQLITE return codes for insert/delete/update/select

ot finding a record where a=100. 3. Return code for a successful INSERT operation will always be SQLITE_DONE. Appreciate your feedback. -- View this message in context: http://old.nabble.com/SQLITE-return-codes-for-insert-delete-update-select-tp31597492p31597492.html Sent from the SQLite mailing li