Feng Forum

Support => Installation problems => : ThorstenW July 09, 2009, 04:25:09 PM

: [1.5b2] DB-Upgrade fails: "specified key was too long..."
: ThorstenW July 09, 2009, 04:25:09 PM

Hi,

was about to upgrade my old test installation to the current beta.
Seems I'm lucky enough to encounter DB upgrade Problems every time ;)

Recent error:

# Database schema transformations executed (total queries: 5)
# OpenGoo has been upgraded. You are now running OpenGoo 1.4.2 Enjoy!
# Upgrade script has connected to the database.
# Test query has been executed. Its safe to proceed with database migration.
#
# Failed to execute DB schema transformations. MySQL said: Specified key was too long; max key length is 1000 bytes
# Error upgrading to version 1.5-beta2

I looked through the "figazza" script but didn't find anything suspicious.

Greetings,
Thorsten

: Re: [1.5b2] DB-Upgrade fails: "specified key was too long..."
: ThorstenW July 09, 2009, 04:41:20 PM

Update:

Tracked it down to the PK creation of the following Table:

CREATE TABLE IF NOT EXISTS `<?php echo $table_prefix ?>template_object_properties` (
`template_id` INT( 10 ) NOT NULL ,
`object_id` INT( 10 ) NOT NULL ,
`object_manager` varchar(255) NOT NULL,
`property` VARCHAR( 255 ) NOT NULL ,
`value` TEXT NOT NULL ,
PRIMARY KEY ( `template_id` , `object_id` ,`object_manager`, `property` )
) ENGINE=<?php echo $engine ?> <?php echo $default_charset ?>;

For now, I created the PK without "property" to get around the limit. (and being able to do further testing ;) )

//edit:
next minor issue:
MySQL said: Unknown column 'is_order_by_asc' in 'og_reports'
at least, quite obvious^^

the rest went through smoothly:
# Database schema transformations executed (total queries: 26)
# 1 public files migrated to upload directory.
# OpenGoo has been upgraded. You are now running OpenGoo 1.5-beta2 Enjoy!

Hope, this feedback is helpful,
Thorsten