Ultimately it'll depend on your schema and the query you're running, but you're probably better off creating an index that covers the SELECT query you're executing. That should make the query fast and save you the hassle of writing and maintaining triggers.
The later post about transactions probably won't help given that you're asking about SELECTs rather than INSERTs/UPDATEs. -T On Mon, Oct 27, 2008 at 5:38 PM, Andrew Gatt <[EMAIL PROTECTED]> wrote: > My program uses a relatively slow select statement to get the rows the > program needs. This is done very often, but updates, inserts and deletes > are done very infrequently. My idea was to create a temporary table with > the result of this select statement, then create triggers from the main > table to update the temporary (or probably just drop and recreate). > > I wanted to know if people thought this was a sensible approach or if > there was another method which was simpler and even faster! > > Andrew > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
