The J! install works like this: <br><br>1 - if the database doesn't exist - it's created.<br><br>2 - if the database exists - and there are existing tables - <br><br>.... a) the existing tables are backed up (default) <br>
<br>.... b) the existing tables are dropped (you have to choose this option)<br><br>The database is never dropped.<br><br><br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 8:40 PM, Andrew Berry <span dir="ltr"><<a href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 14-Nov-08, at 12:23 AM, Dmitri Gaskin wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This has not yet been attempted (I think) simply because most people do not install with a user with sufficient rights to create a database, and therefore there is no need for most people<br>
</blockquote>
<br>
In most setups I've encountered, if you can CREATE DATABASE you can also DROP DATABASE. Not really something I want *any* Drupal install to be able to do :).<br>
<br>
I would actually suggest the other way around, and that if Drupal detects that it can do such things that it sets a warning, just like how it does if the permissions on settings.php are too lax.<br><font color="#888888">
<br>
--Andrew<br>
<br>
</font></blockquote></div><br>