ong # of entries in index IXED_EventDetails
wrong # of entries in index sqlite_autoindex_EventDetails_1
The wrongly-located data was still present afterwards. EventDetails was not
involved in this mis-placed data issue.
James
On 12 April 2011 15:01, James Green wrote:
> Incidentally running prag
On 13 April 2011 15:33, Simon Slavin wrote:
>
> On 13 Apr 2011, at 12:14pm, James Green wrote:
>
>> sync=full does not work well for our app (no transactions). Far too slow.
>
> If you're not syncing, then section 3.2 of the page Richard probably
> indicates w
ansactions). Far too slow.
James
On 13 April 2011 11:47, Richard Hipp wrote:
> On Tue, Apr 12, 2011 at 5:15 AM, James Green wrote:
>
>> My question is does anyone have pointers
>> to help us isolate the problems we are seeing.
>>
>
> http://www.sqlite.org/howtocorru
Another follow-up in the hope someone can shed light on the situation
or ask for further specific testing.
I am told the only thing we change from the default settings is that
synchronous=0. Apparently full mode was far too slow. Reading the
documentation it clearly states that there are limited c
Incidentally running pragma integrity_check on one of the samples I
have been given returns:
*** in database main ***
On tree page 1824 cell 0: invalid page number 218103808
On page 73608 at right child: 2nd reference to page 92497
Page 92110 is never used
Page 92494 is never used
Page 92496 is ne
On 12 April 2011 11:27, Simon Slavin wrote:
>
> On 12 Apr 2011, at 10:15am, James Green wrote:
[ ... ]
> Was it built threadsafe ? See
>
> http://www.sqlite.org/threadsafe.html
Apparently so - the odbc drivers use -DTHREADSAFE=1 when building sqlite.
[ ... ]
> You don't
We have an application that we distribute to our clients each of whom
run Windows - often it's a desktop XP machine. Our app consists of a
set of Delphi services and a PHP web front end each of which use ODBC
for database connectivity.
The vast majority of installations have shipped with sqliteodb
7 matches
Mail list logo
