Greetings!

I have a simple table with five columns and 450,000 rows.  In SQLiteSpy,
I can run "SELECT * FROM trend_data" and get all 450,000 rows in 4.5
seconds.  But in my program, if I use sqlite3_prepare() and
sqlite3_step() until I run out of data, it takes 55 seconds to get
through all rows.  A test with hard-coded junk data showed that my
program is account for only 2 seconds of that.  If I use
sqlite3_get_table(), I can cut my time in half, which is nice, but I'm
still taking 25 seconds to get the same data SQLiteSpy is getting in 4.
How is SQLiteSpy doing it, and can I use the same trick?

Also, my version of the sqlite library code only has an
sqlite3_get_table() method that uses single-byte characters.  Does the
latest code have a Unicode version of this method?

Thank you very much.

Rob Richardson


-----Original Message-----
From: Will Leshner [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 24, 2007 11:39 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] building/upgrading on Mac OS X

On 5/23/07, Alessandro de Manzano <[EMAIL PROTECTED]> wrote:

> That's my question too, and I'm glad to hear it works fine for you :)
> (may I ask you which version of OS X are you using ? the latest 10.4.9
> ?)

Yes. I'm building on a MacBook Pro running 10.4.9.

> I don't understand why on the Wiki's building instructions, Mac OS X
> section, it esplicity says to use --disable-shared for some problem
> with libtool. Maybe some old issue no more applicable ?

I'm not sure about that either. I've been building SQLite "out of the
box" on Mac OS X for several years now and I don't think I've ever had
to do anything more than simply configure and make.

> yep, I tried building "normally" but not tried to install that dynlib
> yet, I'll try as soon as possible :)

I think it should work. At least I hope so :)

------------------------------------------------------------------------
-----
To unsubscribe, send email to [EMAIL PROTECTED]
------------------------------------------------------------------------
-----


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to