Hello all,
First of all, allow me to wish everyone a Happy New Year and I hope it'll be a
good one for all.
My question is (and I've raised this topic back in September, but didn't get
back to it since), does anyone have a free/commercial add-on for SQLite v3 to
perform on-the-fly compression/
The TCL interface to SQLite does not currently support precompiled
statements. Each SQL statement executed is compiled for that one
execution. If the same statement is executed multiple times, it is
compiled multiple times. This note considers ways of addressing
that deficiency.
Incidentally my
On December 31, 2004 06:37 am, D. Richard Hipp wrote:
> Thomas Fjellstrom wrote:
> > It is possible for result items to sit around un finalized for a period,
> > would that cause sqlite to keep a table locked?
>
> In version 3.0.5 and earlier, the commit did not occur until you
> ran sqlite3_finali
On December 31, 2004 06:37 am, D. Richard Hipp wrote:
> Thomas Fjellstrom wrote:
> > It is possible for result items to sit around un finalized for a period,
> > would that cause sqlite to keep a table locked?
>
> In version 3.0.5 and earlier, the commit did not occur until you
> ran sqlite3_finali
MyGeneration is a template based code generator that runs in the Win32
environment. It is 100% free and supports SQLite. There is not yet a set
of templates that generate code for a specific SQLite supported framework,
but the Meta-Data API supports SQLite, so writing your own templates
should be a
On Fri, 2004-12-31 at 08:30 -0500, D. Richard Hipp wrote:
> The issue with the third approach is deciding when to clear the
> precompiled statement cache. Precompiled statements use memory
> and we do not want them to hang around forever.
Why not? Programs that "generate" SQL are often-foolish. P
Thomas Fjellstrom wrote:
It is possible for result items to sit around un finalized for a period, would
that cause sqlite to keep a table locked?
In version 3.0.5 and earlier, the commit did not occur until you
ran sqlite3_finalize(). Beginning with version 3.0.6, the commit
occurs on the last c
The TCL interface to SQLite does not currently support precompiled
statements. Each SQL statement executed is compiled for that one
execution. If the same statement is executed multiple times, it is
compiled multiple times. This note considers ways of addressing
that deficiency.
The most obvious
This has really got me confused. I looked at the locking docs on the sqlite
website, searched the mailing list for answers, but nothing seems to match.
The error message I get says a table is locked, but the error id is just
SQLITE_ERROR (0). I had initially figured it was because I didn't handl
On Fri, 03 Dec 2004 19:04:56 -0500, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
SQLite does not currently support recursive triggers.
On of the main reasons for not supporting recursive
triggers is that disallowing recursive triggers was
seen as the easiest way to avoid infinite loops like
this:
Op vrijdag 31 december 2004 02:23, schreef mike cariotoglou:
> In the home page of www.sqlite.org there is a "contrib" link in the right
> upper area.
> It points to http://www.sqlite.org/contrib
Thanks
Bert
11 matches
Mail list logo