Recent Topics
  1. b2evolution CMS Support Forums
  2. b2evolution Support
  3. General Support
  4. [4.0.3] Can't create table (errno: -1)(Errno 1005)

[4.0.3] Can't create table (errno: -1)(Errno 1005)

1 Jan 19, 2011 20:45    

My b2evolution Version: 4.0.3

Hi,

I tried to install either 3.3.3 and 4.0.3, each hanging during install, after the first table creation attempt. I can create tables in my SQL base, but not as they are defined by b2evolution.

Intallation script adds "ENGINE = innodb" to the SQL command. If I do remove this option, the table creation succeeds.

Is here something wrong with the SQL base? My provider is running MySQL 5.1.41-3ubuntu12.

On the same system, I got another MySQL base and b2evolution 3.3.3. But this was created using a very earlyer b2evoilution installation script.

Regards

P.S.: this is the first SQL command. It doesn't succeed with the option "ENGINE = innodb"

CREATE TABLE evo_groups (
      grp_ID int(11) NOT NULL auto_increment,
      grp_name varchar(50) NOT NULL default '',
      grp_perm_admin enum('none','hidden','visible') NOT NULL default 'visible',
      grp_perm_blogs enum('user','viewall','editall') NOT NULL default 'user',
      grp_perm_bypass_antispam         TINYINT(1) NOT NULL DEFAULT 0,
      grp_perm_xhtmlvalidation         VARCHAR(10) NOT NULL default 'always',
      grp_perm_xhtmlvalidation_xmlrpc  VARCHAR(10) NOT NULL default 'always',
      grp_perm_xhtml_css_tweaks        TINYINT(1) NOT NULL DEFAULT 0,
      grp_perm_xhtml_iframes           TINYINT(1) NOT NULL DEFAULT 0,
      grp_perm_xhtml_javascript        TINYINT(1) NOT NULL DEFAULT 0,
      grp_perm_xhtml_objects           TINYINT(1) NOT NULL DEFAULT 0,
      grp_perm_stats enum('none','user','view','edit') NOT NULL default 'none',
      grp_perm_spamblacklist enum('none','view','edit') NOT NULL default 'none',
      grp_perm_options enum('none','view','edit') NOT NULL default 'none',
      grp_perm_users enum('none','view','edit') NOT NULL default 'none',
      grp_perm_templates TINYINT NOT NULL DEFAULT 0,
      grp_perm_files enum('none','view','add','edit','all') NOT NULL default 'none',
      PRIMARY KEY grp_ID (grp_ID)
    ) ENGINE = innodb DEFAULT CHARSET = latin1

Back to top

2 Jan 19, 2011 20:57

I just checked further. I tried using TYPE = InnoDB, but this is also rejected.

I checked also my server. It seems it supports this option (french, sorry):

InnoDB Documentation

Supports transactions, row-level locking, and foreign keys

[ Variables | Mémoire-tampon | État InnoDB ]

InnoDB est disponible sur ce serveur MySQL. <- means "is available/supported"

Tip 	Répertoire des données 	
	Fichiers de données 	ibdata1:10M:autoextend
Tip 	Auto-croissant: Taille de l'incrément 	8
Tip 	Taille de la mémoire-tampon 	2 048 Mio
	innodb_additional_mem_pool_size 	1 024 Kio
	innodb_checksums 	ON

....

Back to top

3 Jan 20, 2011 00:54

oops... but by the same provider, an early 3.3.3 version is working fine since months.

1005 (ER_CANT_CREATE_TABLE)

Cannot create table. If the error message refers to error 150, table creation failed because a foreign key constraint was not correctly formed. If the error message refers to error –1, table creation probably failed because the table includes a column name that matched the name of an internal InnoDB table.

from http://dev.mysql.com/doc/refman/5.0/en/innodb-error-codes.html

For info also... I could create this table, with "ENGINE=InnoDB":

CREATE TABLE  `demo` (
  `id` int(11) NOT NULL auto_increment,
  `x_id` int(11) NOT NULL,
  `y_id` int(11) NOT NULL,
  `z_id` int(11) NOT NULL,
  `status` tinyint(3) unsigned NOT NULL,
  `created_at` timestamp NOT NULL default CURRENT_TIMESTAMP,
  PRIMARY KEY  (`id`),
  UNIQUE KEY `x_id` (`x_id`,`y_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

[/quote]

Back to top


Form is loading...