Your alternative to sqlite3_mutex_try() doesn't link on NT/2000/XP/Vista
because you still
have TryEnterCriticalSection there instead of getting the pointer to it
dynamically as Nicolas
suggested. So the current mutex_w32.c 1.4 does compile but won't link either.
I suppose this is it:
http://www.ch-werner.de/sqliteodbc/
is this the official driver to use though? The readme file says:
"The driver is usable but may contain lots of memory
leaks and all other kinds of bugs. Use it on your own
risk."
Anyone have any bad experiences with it?
Thanks,
Hi,
Are there are ODBC drivers out there for sqlite on win32? I'm already
using an ODBC library and wanted to see if I could get around
rewriting everything using the native sqlite API.
Thanks,
Mark
-
To unsubscribe,
In the documentation for sqlite3_enable_shared_cache it says:
** Virtual tables cannot be used with a shared cache. When shared
** cache is enabled, the [sqlite3_create_module()] API used to register
** virtual tables will always return an error.
Just curious why is there such a
Just read this today, after doing some other research. Does this help any?
http://www.sqlite.org/faq.html#q6
It says, in a nutshell, don't use a database across forks.
On 10/3/07, John Stanton <[EMAIL PROTECTED]> wrote:
> How do you know that when your process forks that you are looking at the
How do you know that when your process forks that you are looking at the
child, not the parent?
Sabyasachi Ruj wrote:
Hi,
I am writing an application which will continue to execute as a 'daemon' in
Linux.
The application is multi threaded.
And once the daemon is created, it will create few
I have a multi-threaded app, each thread owns it's own DB connection
to a DB it opens for update. Other threads might have the DB open for
reading/writing. From time to time the sqlite_open returns
SQLITE_CANTOPEN on existing DB's. I'm curious about what circumstances
would cause the open to
An index which does not hold keys is not an index. If you don't want to
allocate space for indexing then you put up with slow performance and
use row searches.
[EMAIL PROTECTED] wrote:
I created an index on a TEXT column as I want to be able to
I noticed a large increase in the file size.
Hi,
I am writing an application which will continue to execute as a 'daemon' in
Linux.
The application is multi threaded.
And once the daemon is created, it will create few threads to perform some
tasks.
>From here, I'll refer the 'process before creating the daemon' as 'PARENT
PROCESS',
and
I created an index on a TEXT column as I want to be able to
I noticed a large increase in the file size.
Looking at the binary of the file, I see that the index has a copy of all the
data being indexed.
1. Is this necassary?
2. Is there a way to keep the index only in memory and not in the
L.S.
As per earlier posts: I'm using Sqlite on an Arm architecture without FP-unit
running a kernel that has FASTFPE built in.
After solving the mixed-endian issue, it turns out there's yet another problem
when one is looking at floating point numbers in a text representation..
A number
11 matches
Mail list logo