look at the sql syntax for insert or replace for sqlite.
Also you goal to handle 1 million per minute is probably going to be dependant upon your hardware. For instance throughput greatly increases with disk striping. Also the faster the RPM of the drive the more transactions can be processed. Code it up and find out! --- On Fri, 3/6/09, Nuzzi <nu...@smokemytool.com> wrote: > From: Nuzzi <nu...@smokemytool.com> > Subject: [sqlite] SQLite Transaction Rate and speed... > To: sqlite-users@sqlite.org > Date: Friday, March 6, 2009, 2:27 PM > I have a project where I have to be determining if a row > exists, if so get > the data, change it, and then write it back, if not, then > just writing the > data. I have to be able to do millions of these per > minute. Is that pretty > much impossible with SQLite or any other DB? > > Thanks, > > John > -- > View this message in context: > http://www.nabble.com/SQLite-Transaction-Rate-and-speed...-tp22379931p22379931.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 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users