Re: [sqlite] Why FTS3 has the limitations it does

On Mon, Oct 19, 2009 at 11:25 AM, John Crenshaw wrote: > On the other hand, we could add a tree inside each segment to index the > doclist. The term would be looked up as normal at a cost of O(log nT). > After that though, if the docid is known, it could be looked up at

Re: [sqlite] Why FTS3 has the limitations it does

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wanadoo Hartwig wrote: > It seems to be that ticket 3950 was also closed > (I actually opened this ticket using version 3.6.16). The reason for > closure was that the bug seems to have disappeared It is actually closed. I'm the one who has been

Re: [sqlite] Why FTS3 has the limitations it does

Hi Scott, thanks for the reply. It seems to be that ticket 3950 was also closed (I actually opened this ticket using version 3.6.16). The reason for closure was that the bug seems to have disappeared in version 3.6.19. I have not checked it by myself as I have not installed 3.6.19, yet. I

Re: [sqlite] Why FTS3 has the limitations it does

alf Of Scott Hess Sent: Monday, October 19, 2009 12:51 PM To: General Discussion of SQLite Database Cc: punk...@eidesis.org Subject: Re: [sqlite] Why FTS3 has the limitations it does On Sat, Oct 17, 2009 at 1:25 PM, John Crenshaw <johncrens...@priacta.com> wrote: > Agreed, HUGE thanks for FT

Re: [sqlite] Why FTS3 has the limitations it does

On Sat, Oct 17, 2009 at 1:25 PM, John Crenshaw wrote: > Agreed, HUGE thanks for FTS. Hopefully my original post didn't > come off ungrateful. I was just confused by limitations that > looked like they could have been removed during the initial > design (at least more

Re: [sqlite] Why FTS3 has the limitations it does

Here's a long-ago thread on this: http://www.mail-archive.com/sqlite-users@sqlite.org/msg30540.html Looks like it hasn't been addressed, and I've yet to come up for air on it. There's a ticket out there which looks like the same thing: http://www.sqlite.org/cvstrac/tktview?tn=3338 which is

Re: [sqlite] Why FTS3 has the limitations it does

Am 18.10.2009 um 18:55 schrieb Roger Binns: > Wanadoo Hartwig wrote: >> Slightly different question but related to FTS3. Does anybody know >> why >> this fails using FTS3? > > It isn't failing. Behind the scenes FTS3 is implemented using 3 other > tables (try .dump to see). You are indeed

Re: [sqlite] Why FTS3 has the limitations it does

Wanadoo Hartwig wrote: > Slightly different question but related to FTS3. Does anybody know why > this fails using FTS3? It isn't failing. Behind the scenes FTS3 is implemented using 3 other tables (try .dump to see). You are indeed seeing the last inserted rowid. Roger

Re: [sqlite] Why FTS3 has the limitations it does

Slightly different question but related to FTS3. Does anybody know why this fails using FTS3? CREATE TABLE Simple (ID integer primary key, Name text); CREATE VIRTUAL TABLE SimpleFTS USING FTS3 (Name); CREATE TRIGGER DeleteTrigger AFTER DELETE ON Simple FOR EACH ROW BEGIN DELETE FROM SimpleFTS

Re: [sqlite] Why FTS3 has the limitations it does

users-boun...@sqlite.org] On Behalf Of P Kishor Sent: Friday, October 16, 2009 4:23 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Why FTS3 has the limitations it does On Fri, Oct 16, 2009 at 3:12 PM, Scott Hess <sh...@google.com> wrote: > On Wed, Oct 14, 2009 at 11:3

Re: [sqlite] Why FTS3 has the limitations it does

On Fri, Oct 16, 2009 at 3:12 PM, Scott Hess wrote: > On Wed, Oct 14, 2009 at 11:35 PM, John Crenshaw > wrote: >> The severe limitations on FTS3 seemed odd to me, but I figured I could >> live with them. Then I starting finding that various queries were

[sqlite] Why FTS3 has the limitations it does

The severe limitations on FTS3 seemed odd to me, but I figured I could live with them. Then I starting finding that various queries were giving strange "out of context" errors with the MATCH operator, even though I was following all the documented rules. As a result I started looking deeply into