hi,
this happened on a production system, we created a database with name
X for a given site.

Then we created another site and chosed to create a database for this
new site. Mistakenly we chose X as the database for this NEW site.

Ok, I expected blueonyx to complain about database X already exists...
but no!! Blueonyx simple dropped the old X database, with al it's
information and created a brand new, empty X database.

It simply crapped all the data we had on X.

This should be a common issue. Imagine a blueonyx installation with
100's of sites.. the server admin will not remember which databases
are created and may face the same issue.

Is it possible, before creating a database to simply check if the
database exist, then fail with a message the site creation?

thanks in advance
epe
_______________________________________________
Blueonyx mailing list
[email protected]
http://www.blueonyx.it/mailman/listinfo/blueonyx

Reply via email to