Hello.
I am a newbie both to sqlite and tcl. I would like to learn how to run the
test suite, so that later, when I start modifying the source code (e.g. to
make a customized subset), I can verify that I have not broken anything.
Is there a document somewhere that describes how to run the
Hello everybody,
I am new to this list. We are looking for a sql
database that can run on a 16bit OS. I looked
over the sqlite C source but I found too may
64bit integers, our OS only supports 23 bit longs.
Has someone ported sqlite to a 16bit OS before?
Or maybe someone knows another solution.
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I completed my analysis of the SQLite database memory usage and I
was
surprised to find that SQLite consumes so much memory. I ran my
test
case (creates 31 tables) and found that SQLite consumed 545,231
On Thu, 2007-06-14 at 15:08 -0700, Joe Wilson wrote:
Is there an SQLite 3.x equivalent document for this?
SQLite 2.X Database File Format
http://sqlite.org/fileformat.html
If not, is this 2.x document worth reading as a background to
the general structure of the sqlite 3.x file and
B V, Phanisekhar wrote:
What exactly happens when I change the cache_size (both increase and
decrease size)?
A variable is set.
It seems this term is a misnomer. What are we achieving by setting this
variable?
[...]
Will there be any memory that will be freed up when I reduce the size
Hello Christoph,
Christoph Pross wrote:
Hello everybody,
I am new to this list. We are looking for a sql
database that can run on a 16bit OS. I looked
over the sqlite C source but I found too may
64bit integers, our OS only supports 23 bit longs.
Has someone ported sqlite to a 16bit OS
Hello drh and lists,
Thank you for the information provided at
the ticket page at
http://www.sqlite.org/cvstrac/tktview?tn=2409
Now I successfully worked around the problem.
--
tamagawa ryuji
[EMAIL PROTECTED] :
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I've opened a new ticket 2409.
I sure am glad I converted all SQL to use a BEGIN EXCLUSIVE.
For some reason it struck me as odd that a SQL select could get a SQLITE_BUSY
or even after you perform a single insert operation that a SQLITE_BUSY could
later be thrown.
Is it the delayed mechanism of the Pager Layer that
I am hoping there is an obvious answer to this that I've overlooked.
I have two tables:
create table tableA (path TEXT, value TEXT);
create index myIndexA on tableA (path, value);
create table tableB(path TEXT, value TEXT);
create index myIndexB on tableB (path, value);
Now some simple
You can use something like:
select tableA.path, tableA.value from tableA,tableB where
tableA.path=tableB.path and (tableA.value=tableB.value or
(tableA.value IS NULL AND tableB.value IS NULL));
It's possible that won't use an index, either, due to the OR, in which
case you could try a union
10 matches
Mail list logo