Aaron Stone wrote:
BTW, for performance-conscious folks, converting raw query calls into
functions/procedures could produce a good gain, *especially* in cases
where you're sending multiple commands to do something.
At the very least we want to use prepared statement in the future. There's
a wiki page on the subject called safer_sql.
And I've begun introducing procedures/triggers in the trunk code as well. For
now all it does is update a simple mtime field on the mailboxes table whenever
something changes in the messages table. This already allows us to avoid a lot
of unnecessary queries against the messages table. And the same pattern will
surely apply to many other areas as well.
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
