Yes, I know it sounds a little optimistic :) It's not a problem if I read the whole rowset into memory and then start sending it, but this can cause massive memory usage and time delays. It's not such a big deal if it's not possible, I'll just have to use a Microsoft style progress bar (i.e. one that keeps resetting).
-----Original Message----- From: Will Leshner [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 4:46 PM To: [EMAIL PROTECTED] Subject: Re: [sqlite] Row Count On Aug 11, 2004, at 8:41 AM, Drew, Stephen wrote: > This will be a big overhead on really small queries.... > > I need to be able to say roughly how many rows, but obviously the > exact number would be good. Some queries are very time critical and > complex so I don't want to have to do a COUNT(*) on them. > So you would like a way to get a count of rows a SELECT will return without actually processing the SELECT?
