No, I could do that. I thought it would be easier to maintain and/or allow for easier path to upgrading if it were broken out.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Brandon Adams Sent: Monday, December 13, 2010 4:55 PM To: DBMail mailinglist Subject: Re: [Dbmail] Question: Configurable SQL statements Is there a particular reason you can't just patch the source code in question and make it use whatever (potentially optimized) SQL that you want? On Mon, Dec 13, 2010 at 6:30 PM, Kris Oye <[email protected]> wrote: I have started evaluating dbmail as a mail storage solution in our application. One question whether or not it is possible to override/optimize the SQL statements used when communicating with the underlying database. It appears that all SQL statements are currently hard-coded into the binary. Example: snprintf(__auth_query_data, AUTH_QUERY_SIZE, "SELECT deliver_to FROM %saliases " "WHERE lower(alias) = lower('%s') " "AND lower(alias) <> lower(deliver_to)", DBPFX, escaped_username); Will a future release allow statements to be supplied via configuration file? With an alias table of 750K+ entries this statement can get expensive and I would rather rely on the DB collation and not use lower() at all. Kristian Oye, Sr.. Operations Developer ________________________________________________________ Ekaria LLP Note: This e-mail and any attachments may contain legally privileged confidential information which is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender & delete this message _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
