I should note that there's a gross inefficiency when using triggers to handle updates or deletes against views; SQLite does the equivalent of this:
For UPDATE <view> ... WHERE <condition>, SQLite copies the entire source view into the temp table. SELECT * INTO <temptable> FROM <view> Then, it iterates over <temptable>, looking for rows that match <condition>, and *then* runs the trigger on them. This means that if your source view is large, this will run slowly. I submitted a patch a long while ago to optimize this by turning the initial temp-table population into "SELECT * INTO <temptable> FROM <view> WHERE <condition>", which worked much faster, but I don't think anything came of it. (my original msg to this list: http://readlist.com/lists/sqlite.org/sqlite-users/2/11029.html ) -- -- Stevie-O Real programmers use COPY CON PROGRAM.EXE _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
