Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread jose isaias cabrera
"Daniel Önnerby" wrote, If you attach both databases I guess you can use the replace-command since the uniqueID exists in both databases. REPLACE INTO server.table SELECT * FROM client.table; It would also be helpful to keep a local track of what ID has not been updated on the server yet,

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread jose isaias cabrera
[EMAIL PROTECTED] wrote, "jose isaias cabrera" <[EMAIL PROTECTED]> wrote: Greetings! I have this scenario... 6 users with local dbs 1 network db to backup all those DBs and to share info. Every local DB unique record id based on the network DB. So, before each user creates a new record,

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread jose isaias cabrera
Thanks. - Original Message - From: "Dennis Cote" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Thursday, March 08, 2007 10:24 AM Subject: Re: [sqlite] Fastest way of UPDATE'ing jose isaias cabrera wrote: I have this scenario... 6 users with

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread jose isaias cabrera
Thanks. - Original Message - From: "Daniel Önnerby" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org> Sent: Thursday, March 08, 2007 10:22 AM Subject: Re: [sqlite] Fastest way of UPDATE'ing If you attach both databases I guess you can use the replace-comma

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread drh
"jose isaias cabrera" <[EMAIL PROTECTED]> wrote: > Greetings! > > I have this scenario... > > 6 users with local dbs > 1 network db to backup all those DBs and to share info. > > Every local DB unique record id based on the network DB. So, before each > user creates a new record, the tool

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread Dennis Cote
jose isaias cabrera wrote: I have this scenario... 6 users with local dbs 1 network db to backup all those DBs and to share info. Every local DB unique record id based on the network DB. So, before each user creates a new record, the tool asks the network ID for the next available

Re: [sqlite] Fastest way of UPDATE'ing

2007-03-08 Thread Daniel Önnerby
If you attach both databases I guess you can use the replace-command since the uniqueID exists in both databases. REPLACE INTO server.table SELECT * FROM client.table; It would also be helpful to keep a local track of what ID has not been updated on the server yet, so you do not need to

[sqlite] Fastest way of UPDATE'ing

2007-03-07 Thread jose isaias cabrera
Greetings! I have this scenario... 6 users with local dbs 1 network db to backup all those DBs and to share info. Every local DB unique record id based on the network DB. So, before each user creates a new record, the tool asks the network ID for the next available sequential record and