I found that the sqlite3_open call is not thread safe even if you open
different files in separate connections. Cannot tell you about
sqlite3_close but may be the same problem.
Darío
On Dec 26, 2007 6:40 AM, Pathompong Puengrostham <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a multi-threaded progr
Hello,
I'm trying to compile SQLite 3.5.4 and I'm having the following problem:
first, it does not detect anymore if TCL is present or not, so I added
the --disable-tcl option to the configure, but even with this option
I'm getting the following:
$ configure CC=xlc_r CXX=xlC_r --prefix=/workspac
My application is running 24x7 with huge data loads and around 10 open
connections all the time.
On Dec 19, 2007 4:50 AM, Renaud HUILLET <[EMAIL PROTECTED]> wrote:
>
> I have that for my soft and it works fine.
>
> I also have a swap mecanism to update the sqlite file : the daemon gets the
> sqli
Current implementations of NFS on Linux have a decent lock mechanism
(as far as I know). You'll have to check your NAS device how does it
handle NFS locking.
But, if your NFS device is a complete box and not just a disk array
with an ethernet card, you will be better creating a small
client-server
Hello:
I'm using SQLite 3.4.1 on an AIX 5.3.
I have a file that grew up to 2 GB, now when I try to open it with the
sqlite3 command I cannot, the message is the following:
$ sqlite3 my_file.db
Unable to open database "my_file.db": out of memory
File permissions are ok, user limits are to the
5 matches
Mail list logo