The old server can be accessed through phpMyAdmin at http://www.db4free.net/phpMyAdmin/. Select the 2nd entry (db4free.org:3306) to access that old server. Its availability is sort of limited, it still runs in InnoDB recovery mode (without it, it doesn’t even start up) and Read Only mode. My current plan is to leave the old server like this for another month (i.e. May 27, 2011).
The new server will start over fresh and clean again. So even if you had an account, please register again at http://www.db4free.net/d4f_apply.php.
This new MySQL server goes back to using MyISAM as its default storage engine. I can’t promise that corruptions like the recent one don’t happen again. But if you want to play it a bit safer, stick with MyISAM (which is more likely to be accessible in such a scenario). If you want to create an InnoDB table, simply specify the engine in your CREATE TABLE statement, like so:
CREATE TABLE [table] (...) ENGINE=INNODB;
The rules which were in place on the old server remain in place on the new one as well:
- db4free.net is a testing environment
- db4free.net is not suitable for production
- if you decide to use your db4free.net database in production despite the warnings, you do that at your own risk (very frequent backups are highly recommended)
- data loss and outages can happen at any time (any complaints about that will likely be ignored)
- the db4free.net team is not granting any warranty or liability of any kind
- the db4free.net team reserves the right to delete databases and/or accounts at any time without notice
- it is up to you to get the latest information from the Forum (http://www.db4free.net/forum/viewforum.php?f=1) and the db4free.net blog (http://www.mpopp.net/category/db4free/)