Re: [sqlite] Re: Fastest way to check if new row or update existing one?

2007-12-25 Thread Kees Nuyt
On Tue, 25 Dec 2007 19:24:48 +0100, "Mag. Wilhelm Braun" <[EMAIL PROTECTED]> wrote: >Thanks as in my case just number 2 is possible a quite 'silly' question: >How do you normally check if Update was successful if the specified row >did not exists. > >e.g: UPDATE MyTable SET

[sqlite] Re: Fastest way to check if new row or update existing one?

2007-12-25 Thread A. Pagaltzis
* Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 19:30]: > If row 50 does not exists it does nothing and I seem not to get > any return to know? http://sqlite.org/c3ref/changes.html > using pysqlite. I don’t know anything about pysqlite, but apparently you are looking for the `rowcount`

Re: [sqlite] Re: Fastest way to check if new row or update existing one?

2007-12-25 Thread Mag. Wilhelm Braun
Thanks Pagaltzis. Great help. W.Braun A. Pagaltzis wrote: * Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 19:30]: If row 50 does not exists it does nothing and I seem not to get any return to know? http://sqlite.org/c3ref/changes.html using pysqlite. I don’t know

Re: [sqlite] Re: Fastest way to check if new row or update existing one?

2007-12-25 Thread Mag. Wilhelm Braun
Thanks as in my case just number 2 is possible a quite 'silly' question: How do you normally check if Update was successful if the specified row did not exists. e.g: UPDATE MyTable SET Account='MyAccountName' WHERE ID=50 If row 50 does not exists it does nothing and I seem not to get any

[sqlite] Re: Fastest way to check if new row or update existing one?

2007-12-25 Thread A. Pagaltzis
* Mag. Wilhelm Braun <[EMAIL PROTECTED]> [2007-12-25 15:10]: > QUESTION: is there a better way to make this important > decision? using Sqlite 1. If you are changing the entire row on every update, you can simply use `INSERT OR REPLACE` (assuming there is a UNIQUE column) to always do this