On Nov 30, 2007 9:47 AM, Bill Moran <<a href="mailto:wmoran@potentialtech.com" target="_blank">wmoran@potentialtech.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I expect that the right way to make Drupal _truly_ database neutral is<br>to have database-dependent and database-independent code. You'd only<br>see this kind of thing at the lower levels, and higher logic code<br>
shouldn't even care about it.
<br></blockquote></div><br>The alternatives are:<br><br>1. Calling modules would do 'case' statements for each type of database. No one wants that, unless it is a highly optimized site with lots of customization (
i.e. not the normal Drupal core).<br><br>2. Use the lowest common denominator for SQL and live with performance and scalability issues.<br><br>3. Do database specific stuff (including optimization) in the abstraction layer (this is what Bill Moran advocates above).
<br><br>I am for #3 as the way forward.<br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com" target="_blank">2bits.com</a><br><a href="http://2bits.com" target="_blank">
http://2bits.com</a><br>Drupal optimization, development, customization and consulting.