Op 6-feb-2010, om 18:03 heeft Eric Bohlman het volgende geschreven: > BareFeet wrote: >> In general, I think it's much better (performance and logic) to do >> all you can in SQL, without passing values out of SQL results, into >> your non-SQL code, then re-injecting back into another SQL query etc. > > With SQLite, that's not really going to make a difference. Since > it's an > embedded library rather than an out-of-process server, > "passing/injecting" doesn't require marshalling or network > overhead, so > there's no performance hit. In terms of logic, since SQLite doesn't > have > stored procedures the idea of centralizing database interactions into > the DB itself rather than distributing the logic between applications > isn't applicable here.
If you are in favour of centralizing processing in the database, then an SQLite temporary table could serve as a vehicle for passing results from one query to another. I hope this needs not to much clarification. The first query insert the parameter into the temp table. The other reads it back using a sub-query. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
