Are there any (hehe) plans to implement the ALL and ANY keywords for
testing against subqueries?
What I was told was:
sqlite OLD.db .dump | sqlite3 NEW.db
That didn't work for me on Windows, but
sqlite OLD.db .dump > 2816dump
sqlite3 NEW.db < 2816dump
Did work.
On 8/29/05, Richard Boehme <[EMAIL PROTECTED]> wrote:
>
> I've been looking around the sqlite website and searching Google gr
I've been looking around the sqlite website and searching Google groups
to try to find a migration guide for going from sqlite 2 to sqlite 3.
Can anyone point me to such a guide?
Thanks.
Richard
I've done similar stuff with a commercial grid control. It would call your
code
when it needed data. It would only ask for what was currently visible on the
screen so it was very fast compared with loading all the data at startup. If
they
never look at the stuff at the bottom of the list you neve
Oh, go ahead, be nasty :-) I'm not in favor of the design, either,
but that's what our client wants. Getting confirmation that it's a
poor design helps, too.
We have previously delivered tools that use CSV files instead of a
database. Once you pay the penalty of reading the entire file and
On 8/26/05, Keith Herold <[EMAIL PROTECTED]> wrote:
>
> It's not too hard.
>
> Instantiante a static class method that matches the sqlite callback
> signature.
Yes, I've done it before, and as your instructions show there's a lot of
"fooling
about" to get it done. If you use sqlite_step(), w
On 8/29/05, Aaron Burghardt <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> I'm trying to efficiently display a large table to users. I have a
> test database with 2.7M records that is 1.6 GB in size (though over
> half of that is 6 indexes). My best idea so far has been to display
> one "page" of the
On Fri, 2005-08-26 at 12:53 -0400, Griggs, Donald wrote:
> Regarding Mrs. Brisby's ending comment:
>"A better defense: use a different key each time. Encrypt the session key
> separately."
>
> I may way off in asking this, but:
> Since we're talking about the encyption of data at rest, and a
On Fri, 2005-08-26 at 16:21 +0200, F.W.A. van Leeuwen wrote:
> >
> > The usual defense against this attack is to mix some random information
> > into the beginning of the plaintext.
> >
> > A better defense: use a different key each time. Encrypt the session key
> > separately.
> >
>
> And /or
For problem 1: the order of records from a SELECT is never promised to be
any particular order unless you specify one with ORDER BY. All relational
databases behave this way. Leaving the order up to the database allows them
to be returned in whatever order is the fastest. It isn't surprising tha
I have encountered some problems when upgrading to 3.2.5 from 3.2.2. I am
using the sqlite3.dll from a delphi application (windows xp), not the
sqlite3.exe
1. Order of returned records in a SELECT sometimes is not the same as 3.2.2,
when statement does not have an "ORDER BY". As an inmediate
Hi All,
I'm trying to efficiently display a large table to users. I have a
test database with 2.7M records that is 1.6 GB in size (though over
half of that is 6 indexes). My best idea so far has been to display
one "page" of the database at time, where a page is some arbitrary
number (20K
12 matches
Mail list logo
