On Tue, 2006-08-15 at 12:04 -0500, Jim C. Nasby wrote: > On Tue, Aug 15, 2006 at 09:39:06AM -0700, Aaron Stone wrote: [snip] > > One possible path to making this work is a PHP extension compiled > > against our libdbmail.so library. Most people would rather see a > > pure-PHP solution, however, so you're back at porting weDBMail to the > > current schema... > > What about using stored procs as an API into the database? I know that > raises some cross-database issues, but those aren't insurmountable (and > probably aren't much worse than dealing with the cross-database stuff in > C).
I'm totally open to using stored procedures for certain queries where it makes sense, but I'm not up for rewriting all 154 queries anytime soon! Also, we've been able to reuse all of the queries, swapping in just a handful of specific function names where needed. If we went fully over to stored procedures, because MySQL and PostgreSQL don't (yet?) use the same stored language, we'd be right back in DBMail 1.x land with two totally independent database layers. Aaron
