Re: [sqlite] to get 2 records after a special records. But wrong count, the count is 5

Thanks, I've gotten the point, :) and the next question is that how to know the true count after a special record while getting a special number records. P Kishor-3 wrote: > > On Sun, Mar 21, 2010 at 9:19 PM, liubin liu <7101...@sina.com> wrote: >> >> >> my application is like below. To get

Re: [sqlite] R*Tree and sqlite3_last_insert_rowid() API - possible bug?

On Mar 22, 2010, at 4:16 AM, Wanadoo Hartwig wrote: > Hi Minar, hi Dan, > > there is a similar bug in the FTS3 module. But here the > sqlite_last_rowid may return a wrong value. How do we reproduce this bug? Dan. ___ sqlite-users mailing list

Re: [sqlite] to get 2 records after a special records. But wrong count, the count is 5

On Sun, Mar 21, 2010 at 9:19 PM, liubin liu <7101...@sina.com> wrote: > > > my application is like below. To get 2 records after a special records. But > wrong count, the count is 5: > sqlite> > sqlite> CREATE TABLE t1 (id INTEGER PRIMARY KEY, data INTEGER); > sqlite> INSERT INTO t1 VALUES (3,

[sqlite] to get 2 records after a special records. But wrong count, the count is 5

my application is like below. To get 2 records after a special records. But wrong count, the count is 5: sqlite> sqlite> CREATE TABLE t1 (id INTEGER PRIMARY KEY, data INTEGER); sqlite> INSERT INTO t1 VALUES (3, 999); sqlite> INSERT INTO t1 VALUES (2, 989); sqlite> INSERT INTO t1 VALUES (4,

Re: [sqlite] INTERSECT versus INNER JOIN with latitude, longitude queries

On 3/21/2010 5:22 PM, Max Vlasov wrote: > On Sun, Mar 21, 2010 at 3:50 PM, Tim Romano wrote: > > >> For someone who doesn't read C, could someone who knows please describe >> the SQLite INTERSECT algorithm? What optimizations are available to it? >> Does INTERSECT have

Re: [sqlite] R*Tree and sqlite3_last_insert_rowid() API - possible bug?

Hi Minar, hi Dan, there is a similar bug in the FTS3 module. But here the sqlite_last_rowid may return a wrong value. Regards, Hartwig Am 19.03.2010 um 20:13 schrieb Dan Kennedy: > > On Mar 19, 2010, at 11:04 PM, Minář Petr wrote: > >> Hi, >> I was experimenting a bit with R*Tree extension

Re: [sqlite] Living dangerously.

On Sun, Mar 21, 2010 at 01:03:56PM -0400, Ted Rolle scratched on the wall: > How/where do I set the 'Living Dangerously' flag? Is it case-sensitive? Which one? There are plenty of stupid ways to configure things if you don't understand what you're doing. The most common "dangerous"

Re: [sqlite] INTERSECT versus INNER JOIN with latitude, longitude queries

On 3/21/2010 10:26 AM, Igor Tandetnik wrote: > Tim Romano wrote: > >> For latitude/longitude queries >> > Without diving into the details of your situation, I wonder if you are aware > of R-Tree extension: > > http://www.sqlite.org/rtree.html > Thank you Igor. I had read about

[sqlite] Living dangerously.

How/where do I set the 'Living Dangerously' flag? Is it case-sensitive? -- _ 3.14159265358979323846264338327950Let the spirit of pi 2884197169399375105820974944592307 spread all over the world!

Re: [sqlite] INTERSECT versus INNER JOIN with latitude, longitude queries

Tim Romano wrote: > For latitude/longitude queries Without diving into the details of your situation, I wonder if you are aware of R-Tree extension: http://www.sqlite.org/rtree.html -- Igor Tandetnik ___ sqlite-users mailing list

[sqlite] INTERSECT versus INNER JOIN with latitude, longitude queries

For someone who doesn't read C, could someone who knows please describe the SQLite INTERSECT algorithm? What optimizations are available to it? Does INTERSECT have to assume that neither vector is pre-sorted? Here's the background of my question: For latitude/longitude queries, I was

[sqlite] Fwd: Sqlite User

Begin forwarded message: > From: Alexis Colon > Date: March 21, 2010 1:00:18 AM EDT > To: d...@hwaci.com > Subject: Sqlite User > > Hello. > > please help > how many user at the same time ken use sqlite > > thanks the any help > D. Richard Hipp d...@hwaci.com