Error when creating / renaming tables?

Clean install of latest Jojo RC1. I keep getting this error at point of the setup where it creates the tables within the database.

ALTER TABLE `tag_item` DROP FOREIGN KEY `tag_item_ibfk_1` Error on rename of './pidgeonl_mysite/tag_item' to './pidgeonl_mysite/#sql2-939-ebb81' (errno: -1)

I have tried it three different times to make sure I wasn't missing anything out.

Has anyone else encountered this error before?

Can anyone shed some light on where things may be going wrong?

Thanks everyone for any help you may be able to offer.

Clean install of latest Jojo RC1. I keep getting this error at point of the setup where it creates the tables within the database. ALTER TABLE `tag_item` DROP FOREIGN KEY `tag_item_ibfk_1` Error on rename of './pidgeonl_mysite/tag_item' to './pidgeonl_mysite/#sql2-939-ebb81' (errno: -1) I have tried it three different times to make sure I wasn't missing anything out. Has anyone else encountered this error before? Can anyone shed some light on where things may be going wrong? Thanks everyone for any help you may be able to offer.

this is installing into a fresh/empty database?
what version of mySQL are you using? on what platform?

this is installing into a fresh/empty database? what version of mySQL are you using? on what platform?

Yes fresh db.

Running PHP 5.2.6 / MYSQL 5.0.51 / Apache 2.2.9

Its a hosted site running on the above. Not local dev.

Yes fresh db. Running PHP 5.2.6 / MYSQL 5.0.51 / Apache 2.2.9 Its a hosted site running on the above. Not local dev.

If its of any interest the issue is with any table running the InnoDB engine.

Which with JoJo means the tag and tag_items tables and also the flags / fields (???) table that is currently in the nightly builds version.

If its of any interest the issue is with any table running the InnoDB engine. Which with JoJo means the tag and tag_items tables and also the flags / fields (???) table that is currently in the nightly builds version.

Can you try making a test InnoDB table in phpmyadmin and see if you can successfully add a bunch of rows to it?

We haven't seen any issues like this before, so would like to eliminate the possibility of it being something to do with your particular MySQL setup rather than Jojo itself.

Can you try making a test InnoDB table in phpmyadmin and see if you can successfully add a bunch of rows to it? We haven't seen any issues like this before, so would like to eliminate the possibility of it being something to do with your particular MySQL setup rather than Jojo itself.

#1034 - Incorrect key file for table 'test1'; try to repair it

I get a similar error with the default jojo tag, tag_item tables.

#1034 - Incorrect key file for table 'tag_item'; try to repair it

Have tried on two different host accounts with the same host (hostingdirect.co.nz) and get the same error on both.

#1034 - Incorrect key file for table 'test1'; try to repair it I get a similar error with the default jojo tag, tag_item tables. #1034 - Incorrect key file for table 'tag_item'; try to repair it Have tried on two different host accounts with the same host (hostingdirect.co.nz) and get the same error on both.

so you got an error when setting up/modifying a new InnoDB table on a fresh datatabse (ie not through anything to do with Jojo)?

If so, it sounds like there may be issues with the MySQL install - Googling that error code comes up with a bunch of old issues, some to do with a buggy alpha of MySQl , but others are to do with the OS it's running on not supporting InnoDB file sizes:
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.

In which case, do they have a helpdesk you can ask to see whether it's a known issue?

so you got an error when setting up/modifying a new InnoDB table on a fresh datatabse (ie not through anything to do with Jojo)? If so, it sounds like there may be issues with the MySQL install - Googling that error code comes up with a bunch of old issues, some to do with a buggy alpha of MySQl , but others are to do with the OS it's running on not supporting InnoDB file sizes: InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. In which case, do they have a helpdesk you can ask to see whether it's a known issue?

Yes tried with a fresh DB.

Have hit up the support team and will let you know the outcome.

Yes tried with a fresh DB. Have hit up the support team and will let you know the outcome.