On Sat, Apr 1, 2017 at 10:22 PM, Jeffrey Mattox <j...@mac.com> wrote:
> >> On Apr 1, 2017, at 10:43 PM, J Decker <d3c...@gmail.com> wrote:
> >
> > I can add an idle sweep to close connections when nothing has been in
> progress for a while.... but only on sqlite connections which complicates
> things...
>
> Why don't you do as Simon suggested ("the application should have the
> SQLite database open only while it’s being accessed.")? That is, open a
> connection to the DB when you need to access it and then immediately close
> the connection?
>
> have you never watched the hoops operating systems go through to open
files? That's a LOT of work that takes a million inserts a second to a few
10k...
oh - you mean on a higher level? Oh because my api just allows doing sql
commands without specifying a connection; so typically I don't know when
it's 'done'... the connection is either availalble or it's not... but then
again most normal programs just gracefully exit and don't just cease
functioning.
I actually already had that avaiable, I just needed to enable it.
> Jeff
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
