i placed a poll in this story here, but it's is not possible, to place a comment there.

if this is already fixed in the current cvs just ignore this/delete this/bitch at me: i often get outdated antville pages; most of the time i have to hit reload, sometimes i don't notice and edit a story with outdated text in the edit form and, for example, put an old typo back in when fixing a second one. i put this line

<meta http-equiv="pragma" content="no-cache">

in the main skins of my local project logs and my antville.org site, which seems to prevent my browsers from caching anything nicely, but doesn't help convince the proxy i have at the office to reload every page.

question 1: what else can i do so don't have to reload my own pages? question 2: once we found something that works, wouldn't it be nice to have it in every antville main skin by default, so no one has to manually reload any page any more? :-)

around 1:30 AM CET tonight. Did some tuning on the database server. We hope this will result in a healthier, faster Antville and we keep our fingers crossed that this may have been the last outage for some time to come.

The management.

As a look into /var/lib/mysql/adele-slow.log shows, the AV_TEXT table is in the center of a lot of performance problems we're seeing here on antville.org. Looking for a fix I stumbled across PROCEDURE ANALYSE(), which is a very nice MySQL feature that tells you how database columns are currently utilized and what type definition MySQL would propose for those columns. The statement

SELECT * FROM AV_TEXT PROCEDURE ANALYSE(16,256)

produces a few interesting results:

Column	Old type	Proposed type
TEXT_DAY	varchar(10)	INT(8) UNSIGNED
TEXT_PROTOTYPE	varchar(20)	ENUM('comment','story') NOT NULL
TEXT_TITLE	mediumtext	TEXT
TEXT_TEXT	mediumtext	CHAR(0)

I've tried them these out on my local installation and they seem to work fine, so I'm checking them into CVS and will eventually update the DB on antville.org

I am ready for donations or a "premium membership fee" in order to help antville improve. The more I use antville the more valuable antville becomes.

From time to time when i take a link to get to an antville log i get 'maximum count reach...'. After refreshing the load it works mostly. Before updating it didn´t happen. Is it a question of system ressources? And what about the hardware. How i remember (?) there is only a quite small Harddisk to work on. It should not be a such big prob to find a solution. I think, that a lot of antvillians would join helpin' to keep antville on work...

When contributing e.g. a comment to a German-language antville-blog, the following confirmation message is returned: "der Kommentar wurde erfolgreich gespeichert". Same thing in English: "the story was created succesfully". Since I don't think that there is such a thing as unsuccessful saving or creation of stories ("der Kommentar wurde erfolglos gespeichert", "the story was created without success"), the adverb "erfolgreich"/"successful" is redundant, and, if you don't mind me saying this, actually also sounds a bit silly. It's not at all a big issue, but perhaps a correction could be made to these confirmation messages in future releases - just for the linguistically picky :-)