On Tuesday, 22 January, 2013 19:14 MST, Ward Willats
wrote:
> On Jan 22, 2013, at 5:54 PM, Keith Medcalf wrote:
>> In my case, I only have one writer (I think!) during the big transaction,
>> so a long-lived, singleton connection or WAL should
On Tuesday, 22 January, 2013 19:14 MST, Ward Willats
wrote:
> On Jan 22, 2013, at 5:54 PM, Keith Medcalf wrote:
>> I prefer the long-lived approach. Continuously re-initialization of the
>> connection on open, the need to re-read pages into the
On Jan 22, 2013, at 5:54 PM, Keith Medcalf wrote:
> I prefer the long-lived approach. Continuously re-initialization of the
> connection on open, the need to re-read pages into the page cache
> repetitively, and the subsequent discard of a nicely loaded page-cache on
>
> All is well, EXCEPT, I have ONE big, long transaction that collects and
> stores a lot of data from some sensors. If this data is big enough, it
> will eventually cause that connection to obtain an exclusive lock on the
> DB. Now if the data collection code subsequently calls any subroutine
Thanks, Dominique
I will try asap, but looking at the arithmetics
25 (The length of "Page ? is never used")
*
800 (maximum I could get)
= 20,000 (limit mentioned in the ticket )
looks like this is a winner :)
Max
> Hi Max
>
> It looks perhaps like the bug that was fixed in this
On Jan 22, 2013, at 10:07 AM, Simon Slavin wrote:
> Change the code used in your one big thread so that it counts the number if
> INSERT/UPDATEs it does and changes transactions and does a little pause after
> every thousand ops. Or hundred. Whatever.
>
Cool idea,
On 22 Jan 2013, at 5:39pm, Ward Willats wrote:
> I have a bunch of home-grown C++ wrappers for Sqlite and when my app needs to
> use the DB, most routines just instance one of these DB wrapper objects on
> the stack and go for it. The constructor creates a new DB
Hello.
Just wondering what the group opinion is on something.
I have a bunch of home-grown C++ wrappers for Sqlite and when my app needs to
use the DB, most routines just instance one of these DB wrapper objects on the
stack and go for it. The constructor creates a new DB connection, which is
On 22 Jan 2013, at 3:30pm, Tal Tabakman wrote:
> a user of mine (run under Linux) encountered SQLITE_IOERR_FSTAT error while
> trying to use our application.
> what could be the reasons for such an error ?
That result code is meant to be triggered by the following
Max Vlasov wrote:
> Hi,
>
> I found with the web search that this error (out of memory for PRAGMA
> integrity_check) appeared in the wild and there were some fixes related to
> it.
>
> Today I decided to do the check for a base that lives with its own
> encrypted vfs and with an sqlite version
10 matches
Mail list logo