Hi,
sorry, but I thought that there would have been an automatic conversion to a
float. The comparison is not 1 but a floating point literal like 1.0.
Am 12.12.2010 um 03:49 schrieb Richard Hipp:
> On Sat, Dec 11, 2010 at 7:07 PM, Wanadoo Hartwig <
> hartwig.wiesm...@wanadoo.
Hi,
take the following SQL statement:
UPDATE tableA SET column1=(SELECT column2 FROM tableB WHERE function1(column3)
< 1 ORDER BY function1(column3) LIMIT 1);
Actually, this statement does not make sense because the ORDER BY expression
does not fulfill the requirements of an ORDER BY expressio
These statements
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 WHERE (rowid=OLD.ID); END;
CREATE TRIGGER InsertTrigger AFTER INSERT ON Simple
Hi Dan,
Am 22.03.2010 um 05:08 schrieb Dan Kennedy:
>
> 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.
>
>
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
Am 26.10.2009 um 18:49 schrieb P Kishor:
> On Mon, Oct 26, 2009 at 12:40 PM, Wanadoo Hartwig
> wrote:
>>
>> Am 26.10.2009 um 15:27 schrieb P Kishor:
>>
>> On Mon, Oct 26, 2009 at 9:17 AM, Scott Hess wrote:
>>
>> The bug was closed with "cannot r
ways the one that caused the trigger to fire
(in case of an insert trigger). Furthermore, I checked the
documentation concerning virtual tables and there is no exception
mentioned that virtual tables should behave differently than normal
tables with respect to triggers (besides the statement
Hi Roger,
Am 25.10.2009 um 18:47 schrieb Roger Binns:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>>> can you please re-open the ticket? This bug only occurs in
>>> combination with FTS3. Using normal tables in triggers does not
>>> cause
>>> any problems.
>
> The underlying cause is th
Hi Roger,
I just downloaded SQLite3 version 3.6.19 and did the same testing as I
did before:
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
;
> There's a ticket out there which looks like the same thing:
> http://www.sqlite.org/cvstrac/tktview?tn=3338
> which is closed, but it sounds like if you put up a simple repro-case
> you might get a re-hearing on it.
>
> -scott
>
>
> On Mon, Oct 19, 2009 at 9:13 AM,
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
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
Am 30.08.2009 um 17:56 schrieb Kit:
> 2009/8/29 Wanadoo Hartwig :
>> The largest and last row id is 4. Why is SQLite returning 5? I think
>> it has to do with the FTS3 module but still the trigger statement
>> should shield the row ids from the trigger statement, or?
>&g
Hi,
last time I have posted this bug(?) using an C-API. Here is the same
bug(?) using only SQL statements:
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 F
Hi Simon,
I am not complaining about the autoincrement's result but that
sqlite3_insert_rowid returns the wrong rowid.
Hartwig
Am 29.06.2009 um 23:09 schrieb Simon Slavin:
>
> On 29 Jun 2009, at 8:54pm, Wanadoo Hartwig wrote:
>
>> I have posted a while ago a bug (at leas
Hi,
actually, I also tested it with 3.6.16 and the bug still exists.
Hartwig
Am 29.06.2009 um 21:54 schrieb Wanadoo Hartwig:
> Hello,
>
> I have posted a while ago a bug (at least I think that it is a bug)
> but only in a very abstract form. Now, I have written a C-program
>
Hello,
I have posted a while ago a bug (at least I think that it is a bug)
but only in a very abstract form. Now, I have written a C-program
showing the bug.
Brief description:
An FTS related trigger combination leads to a wrong determination of
the last inserted row id. Triggers that are
17 matches
Mail list logo
