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. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
