Error prevents DB deployment via sql-sync or manual import

Have the same issue on http://simplytest.me/

This bug also makes it impossible to install Dupal Commons on MyISAM as panelizer is a dependency
#1818788: Installer errors without InnoDB enabled

This is weird. Does anyone have any insight into which key is failing? In just looking at this, I don't see any keys that are as big as innodb is saying.

My best guess is that something isn't quite right during an upgrade process. Can you give me the entire create table query that it's trying to run when you import your table? Maybe that will help identify what is broken here.

This is the full error:

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes: CREATE TABLE {panelizer_entity} ( `entity_type` VARCHAR(255) NOT NULL COMMENT 'The type of the entity this panel is attached to.', `entity_id` INT NOT NULL DEFAULT 0 COMMENT 'The entity ID this panel is attached to.', `revision_id` INT unsigned NOT NULL COMMENT 'The revision id of the entity.', `name` VARCHAR(255) DEFAULT NULL COMMENT 'The name of the default being used if there is one.', `no_blocks` TINYINT DEFAULT 0 COMMENT 'Whether or not the node disable sidebar blocks.', `css_id` VARCHAR(255) DEFAULT '' COMMENT 'The CSS ID this panel should use.', `css` LONGTEXT DEFAULT NULL COMMENT 'Any CSS the author provided for the panel.', `pipeline` VARCHAR(255) DEFAULT 'standard' COMMENT 'The render pipeline this panel uses.', `contexts` LONGTEXT DEFAULT NULL COMMENT 'The contexts configured by the node author.', `relationships` LONGTEXT DEFAULT NULL COMMENT 'The relationship contexts configured by the node author.', `did` INT NOT NULL COMMENT 'The display ID of the panel.', `view_mode` VARCHAR(128) DEFAULT NULL COMMENT 'Contains the view mode this panelizer is for.', `css_class` VARCHAR(255) DEFAULT '' COMMENT 'The CSS class this panel should use.', `title_element` VARCHAR(255) DEFAULT 'H2' COMMENT 'The HTML element the title should use.', `link_to_entity` TINYINT DEFAULT 1 COMMENT 'Whether or not the title should link to the entity.', PRIMARY KEY (`entity_type`, `entity_id`, `revision_id`, `view_mode`) ) ENGINE = InnoDB DEFAULT CHARACTER SET utf8 COMMENT 'Node panelizer references.'; Array ( ) in db_create_table() (line 2688 of /home/sb0d09bae91c9f4b/www/includes/database/database.inc).

If I comment all the keys of panelizer_entity out
//'primary key' => array('entity_type', 'entity_id', 'revision_id', 'view_mode'),
Then it works!

If I comment the 'entity_type' key out
It works!

Commenting out any of the other keys still produces the error.

So it's 'entity_type' which makes trouble...
If I change the 'size' of 'entity_type' from 255 to 50 - it works!
100 - still works
128 - works
150 - still works
200 - still works
250 - fails with key too long error

Solution is simple:
Change 'entity_type' size to varchar(128) (the same size as for tables in core)

Patch attached - earl, you will get free beer in prague if this gets committed quickly ;-)

This needs a hook_update_N() implementation to modify the existing column.

patch attached -- add hook_update_7110() to update the entity_type field length.

Patch unfortunately fails
Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT NULL, ADD PRIMARY KEY (`entity_type`, `entity_id`, `revision_id`, `view_' at line 1: ALTER TABLE {panelizer_entity} CHANGE `entity_type` `entity_type` DEFAULT NULL, ADD PRIMARY KEY (`entity_type`, `entity_id`, `revision_id`, `view_mode`); Array ( ) in db_change_field() (line 2988 of /home/patrickd/www/drupal7/includes/database/database.inc).

whoops

Awesome, thanks that one works! :)

Committed and pushed.

Thanks!
This is a pretty critical bug for people using MyISAM, could we make a new release with this?

Yes, I plan on making a new release pretty soon.

uhm how soon? panelizer, panopoly and many others are submitted quite often on simplytest.me, it's a pitty they still don't work as there's no release yet :/

Just reopening as I had the same issue but luckily for me I could just uninstall the module then reinstall.

There is no point in re-opening an issue that had a patch committed and pushed already, on 11/29.