I've finished the new database-schema and updated Antville in CVS. Basically the following has changed:

• There are now three SQL-scripts for creating the Antville-database: for mySQL, for Oracle and for hsqldb (the latter is currently outdated because it creates the old db-schema). Due to some special features in mySQL (id-autoincrement and the timestamp-columntype) the Oracle-script will also create a sequence and two triggers (on the table AV_ACCESS). I also included a template for db.properties if you want to use an Oracle-database. (for details reg. the new database-schema, have a look here. There is also a db-patch that will convert an existing mySQL-database to the new schema (see below!)
• some of the protoypes were renamed to match the names of the database-tables: weblog -> site goodie -> file goodiemgr -> filemgr member -> membership membership -> membermgr this also changes the macro-handlers, eg. the macro <% weblog.title %> is now called <% site.title %>. the default-skins have changed too according to this (same with goodie). For consistency-reasons i've also renamed some macros and functions.
• Most of the stuff that 'til now was defined in app.properties can now be defined via a setup-page. Antville will check if it has been setup'ed and redirect you to /manage/setup if not. It's now also possible to change the language of the whole Antville-Installation, to define a "system title" that will be used instead of "Antville" (mostly in page-titles and confirmation mails).
• It's not possible anymore that an admin of a weblog can "degrade" himself to a lower permission-level. this means that there will always be at least one membership with admin-rights.

IMPORTANT: Due to the new database-schema i do not recommend you to update antville now if you are seriously using Antville. If you already have some weblogs in your database they will throw some errors because the macro-handlers have changed. And most likely the skins that are stored in the database will do so too. We will soon come up with some scripts that will do the update of your data. For testing this version of Antville you should use a newly created database.

I hope this update works fine, but if you encounter bugs please report them here in the project log.

i read out some numbers from the database that indicate the growth of antville.org by weblogs, users and texts.

+-------+-----------+------------+---------------+
| MONTH | NEW BLOGS | NEW USERS  | NEW TEXTS     |
+-------+-----------+------------+---------------+
| Jan   |  64       | 178        |  3675         |
+-------+-----------+------------+---------------+
| Feb   |  81 (+17) | 251 (+ 73) |  5332 (+1657) |
+-------+-----------+------------+---------------+
| Mar   | 161 (+80) | 480 (+229) |  8809 (+3477) |
+-------+-----------+------------+---------------+
| Apr   | 190 (+29) | 453 (- 27) | 11616 (+2807) |
+-------+-----------+------------+---------------+
| May   | 252 (+62) | 594 (+141) | 14473 (+2857) |
+-------+-----------+------------+---------------+
| Jun*  | 311 (+59) | 794 (+200) | 17087 (+2614) |
+-------+-----------+------------+---------------+

• partial results only.

It happens again & again that I'm not content with the name of a topic I created. It would be great to be able to edit a topic's name instead of having to reassign all the stories of a topic to the different name...

...not really important, just a little touch of additional conveniance.