The other place that could benefit from checking which engines are <br>available is the temporary table query in db_query_temporary()<br><br>It now has:<br><br>$query = preg_replace('/^SELECT/i', 'CREATE TEMPORARY TABLE '.
<br>$tablename .' Engine=HEAP SELECT',<br><br>Would be great to check if HEAP (Memory) exists first before doing so.<br><br>So common code for engine checking can be reused.<br><br><div><span class="gmail_quote">On 6/5/07,
<b class="gmail_sendername">James Walker</b> <<a href="mailto:walkah@walkah.net">walkah@walkah.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 6/4/07 5:36 AM, Dries Buytaert wrote:<br>><br>> On 04 Jun 2007, at 05:11, Khalid Baheyeldin wrote:<br>>> An option at install time, such as a drop down list of engines that<br>>> are supported on the server, and selecting one is more appropriate.
<br>>> It will require preg stuff to change the engine. Or using the new<br>>> schema, we can add that more elegantly (not sure how hard would<br>>> it be, but can't be that hard).<br>><br>> I agree with this. Make it an option in the 'advanced settings'
<br>> fieldset on step 3 of the installer (setup database).<br><br>+1 - Yeah, drop down should only include available engines, and it<br>should be fairly simple to add thanks to schema.<br><br>--<br>James Walker :: <a href="http://walkah.net/">
http://walkah.net/</a> :: <a href="mailto:xmpp:walkah@walkah.net">xmpp:walkah@walkah.net</a><br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com
</a><br>Drupal development, customization and consulting.