or 1 thread...or 60000000 threads...makes no difference whatever. Unless you changed the default from SERIALIZED to something that does not apply.
--- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >[email protected]] On Behalf Of Deon Brewis >Sent: Sunday, 27 May, 2018 16:50 >To: SQLite mailing list >Subject: Re: [sqlite] database locked on select > >By one connection doing SELECT and UPDATE, do you mean multi-threaded >mode and using the connection from 2 threads? > >- Deon > >-----Original Message----- >From: sqlite-users <[email protected]> On >Behalf Of Simon Slavin >Sent: Sunday, May 27, 2018 3:39 PM >To: SQLite mailing list <[email protected]> >Subject: Re: [sqlite] database locked on select > >On 27 May 2018, at 7:30pm, Torsten Curdt <[email protected]> wrote: > >> I am doing a select, then iterate through the resultset and on each >> row call update on that row. >> I am using the golang driver and ran into the issue that on the >update >> the database is still locked from the select. > >Are you usihg one connection to do both the SELECT and the UPDATE ? >Or are you using two different connections, one for the SELECT and >one for the UPDATE ? > >The second method will not work. The SELECT connection has the >database locked until you tell your interface you have finished with >the SELECT. > >Simon. >_______________________________________________ >sqlite-users mailing list >[email protected] >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >_______________________________________________ >sqlite-users mailing list >[email protected] >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
