Version 2.8.10 of SQLite is now available on the website.
http://www.sqlite.org/
This version fixes a critical locking bug in Unix. It turns out
that any call to close() clears all locks on file that was closed
(who knew?) which then left the database vulnerable to corruption
from other
At 07:17 PM 1/13/2004 -0500, D. Richard Hipp wrote:
Actually, SQLite implements JOIN USING by translating the
USING clausing into some extra WHERE clause terms. It does
the same with NATURAL JOIN and JOIN ON. So while those
constructs might be helpful to the human reader, they don't
really make
Can anyone suggest a good way to optimize the following query?
SELECT count(*) FROM propositions p, output o
WHERE p.verb_id=o.verb_id
AND p.tag=o.tag
AND (p.stop!=o.stop OR p.start!=o.start);
CREATE INDEX whatever ON output(verb_id,tag);
That will make it O(NlogN) instead of O(N**2).
>
At 05:16 PM 1/13/2004 -0600, Williams, Ken wrote:
SELECT count(*) FROM propositions p, output o
WHERE p.verb_id=o.verb_id
AND p.tag=o.tag
AND (p.stop!=o.stop OR p.start!=o.start);
I don't think this will be much help and is very implementation specific, I
expect, but
Your first two
Bonjour,
I'm creating a tasks management DB in SqLite.
It should be used from ODBC clients as ell as from native SqLite GUIs
(SqLitePlus, DbManager, custom Python apps).
I looked for info on the web regarding the best choice for storing dates and
time.
Choice is not evident.
Should I use
5 matches
Mail list logo
