? Does sqlite3 use table level locking ?
Regards,
Roushan
--
Gé Weijers
e-mail: [EMAIL PROTECTED]
e that case as well (or ignore the error from COMMIT)
*/
issueQuery("COMMIT;");
}
--
Gé Weijers
e-mail: [EMAIL PROTECTED]
Sean Heber wrote:
>
>
> My database file is only around 4MB and I have set the
> default_cache_size to 5. From what I've read, that should
> translate to almost 50MB of cache size which would be more than
> enough to keep the entire database in memory, I'd think. Yet it
> doesn't seem
John Buck wrote:
> MySql works like you described.. Frankly im surprised Postgres doesn't .
> Id imagine there must be a "continue trnasaction" command or something.
You can define a 'savepoint' inside a transaction. If something goes
wrong you roll back to the savepoint and continue from
Vladimir,
When you execute individual statements and sqlite3_step or sqlite3_exec
returns an error code you should execute a 'ROLLBACK' in stead of a
'COMMIT'. So the logic is:
exec "BEGIN"
perform a bunch of statements
if(all statements successful)
exec "COMMIT"
else
exec "ROLLBACK"
Greg Miller wrote:
> Thomas Briggs wrote:
>
>>
>>
>>> From the looks of this warning, I would guess that you could redefine
>>> SQLITE_STATIC like this (or some variation of this that is legal C++)
>>> to solve
>>> the problem:
>>>
>>> #define SQLITE_STATIC ((extern "C" void(*)(void*)) 0)
Tomas Franzén wrote:
> Hi,
>
> I'm using SQLite to access a database that is created and used by
> another application. Sometimes when I try to access it, I get an error
> back that the database is locked. This lock seems to be pretty long
> lasting, so I don't think I can't wait until it's
Ulrik Petersen wrote:
> Hi Gerry,
>
> Gerry Blanchette wrote:
>
>> Greetings All,
>> In general, is passing NULL to sqlite3_bind_text() as parameter 5 valid,
>> instead of using either SQLITE_STATIC or SQLITE_TRANSIENT? (My bind
>> value is a heap pointer which I manage).
>>
>> I ask because on
Same thing on Mac OSX. Must be a platform-independent issue.
Gé
Richard Boulton wrote:
>Hi,
>
>I'm running the latest sqlite 3.2.1 command line tool on Windows XP and have
>noticed that I don't seem to be able to store 48bit integers anymore :-S
>
>CREATE TABLE test (a INTEGER);
>INSERT INTO
Maksim Yevmenkin wrote:
>
>>>so, just with plain ascii file i get four times the speed i get with
>>>sqlite. note that my c program will scale linearly with the size of
>>>dataset (just like i see with sqlite).
>>>
>>>
>> With anything related to computers, there are always tradeoffs -
Maksim,
Some things you could try:
1) increase cache memory
You may be causing a lot of cache misses if the size of the query result
is very large compared to the size of the cache. Index-based searches
can cause multiple reloads of the same page because of a lack of
locality in the cache. An
Jonathan Zdziarski wrote:
>
> D. Richard Hipp wrote:
>
>> Are you sure your users are not, in fact, filling up their disk
>> drives?
>
>
> nope, plenty of free space on the drives. The 50MB limit seems to be
> very exact as well...exactly 51,200,000 bytes. I'm stumped too.
Assuming your
12 matches
Mail list logo