/3/2010 6:53 AM
> To: General Discussion of SQLite Database
> Subject: EXTERNAL:Re: [sqlite] How to write the trigger?
>
>
>
> Is a to-be-inserted row supposed to be included among the counted rows in a
> BEFORE INSERT trigger? Could you end u
);
sqlite> select * from c;
1
2
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Northrop Grumman Information Systems
From: sqlite-users-boun...@sqlite.org on behalf of Tim Romano
Sent: Tue 8/3/2010 6:53 AM
To: General Discussion of SQLite Da
Is a to-be-inserted row supposed to be included among the counted rows in a
BEFORE INSERT trigger? Could you end up with 5 rows? What happens if you
make this an AFTER trigger?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/
Could your trigger be running into the syntax restriction described below?
I'm not sure if the restriction actually applies to your circumstance -- not
sure whether LIMIT and ORDER BY are invalid *anywhere* in a statement in a
trigger that deletes a row, i.e. invalid also in a subquery, as you have
I created a table like this：
CREATE TABLE record_trip (trip_id CHAR(1), gp_no CHAR(1), rec_date INTEGER,
trun CHAR(1), ctrl_id CHAR(1), moment_value INTEGER, minutes_value INTEGER,
set_value INTEGER );
CREATE UNIQUE INDEX i_record_trip ON record_trip (trip_id, gp_no, rec_date);
And the trigger l
5 matches
Mail list logo
