Feng Forum
Support => Older versions => : fcoauga July 05, 2009, 07:39:08 PM
-
I tried install and obtain this:
Step 4: Finish
Installation process:
Database connection has been established successfully
Failed to import database construction. MySQL said: Declaracion de clave demasiado larga. La maxima longitud de clave es 1000
-
Hi,
This seems to be a mysql bug when adding an index to a table.
Try removing the line
ALTER TABLE `<?php echo $table_prefix ?>mail_contents` ADD INDEX `uid`(`uid`);
from '/public/upgrade/templates/db_migration/1_5_figazza.php'
to avoid adding this index, and if it works, try adding the index manually after the update.
regards
-
Sorry, but in this case, it was a new installing, not an upgrade.
-
Test with your instructions without result.
Is a problem with MyIsam access… I had checked with InnoDB delect and works fine.
Note that I am working over the “Easy PHP” package, perhaps it has a “little” configuration…
-
Was the install working before 1.5 on your settings? Please try with version 1.4.2.
Just in case, you could try deleting line 667 of file 'public/install/installation/templates/sql/mysql_schema.php':
KEY `uid` (`uid`)
-
In this check, this is the new error...
Step 4: Finish
Installation process:
Database connection has been established successfully
Failed to import database construction. MySQL said: Algo est� equivocado en su sintax cerca ') ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci' en la linea 31
and in this case, selecting Innodb has the same result.
All this is with a new installation. In the same server, I had checked an upgrade from 1.4.1 (running fine) to 1.5. With a few problems (http://forums.opengoo.org/index.php?topic=2142.0), finally works ok.
My pack is EasyPHP 2.1 (apache 2.2.3+php 5.2.0+mysql 5.0.27) without changes
Today I had checked with the recent pack EasyPhp 3.0 (apache 2.2.11+php 5.2.8+mysql 5.1.30) without changes and with the same results
EasyPHP makes Opengoo totally portable in a USB stick: is a great and simple choice for tests!!
-
Now, I have this problem upgrading too.
With version 1.5.beta1 I had upgraded with a few problems but no this.
Now, this is the result for upgrading 1.4.1 to 1.5.beta3
Config file found and loaded.
File '/config/config.php' exists and is writable
Folder '/config' exists and is writable
Folder '/public/files' exists and is writable
Folder '/cache' exists and is writable
Folder '/tmp' exists and is writable
Folder '/upload' exists and is writable
Extension 'mysql' is loaded
Extension 'gd' is loaded
Extension 'simplexml' is loaded
Upgrade script has connected to the database.
Test query has been executed. Its safe to proceed with database migration.
Upgrade script has connected to the database.
Test query has been executed. Its safe to proceed with database migration.
Database schema transformations executed (total queries: 2)
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: Declaracion de clave demasiado larga. La maxima longitud de clave es 1000
Error upgrading to version 1.5-beta3
-
Hey boys...
I believe that here is the problem:
http://bugs.mysql.com/bug.php?id=4541 (http://bugs.mysql.com/bug.php?id=4541)
Maybe I'm doing something wrong with my backup, but what is the problem with a new installation?
Sure that is a little problem for you... ;D
-
Firt of all: I´m not a progammer (my experience is only with basic:
;D zx spectrum basic
::) quick basic 4.5
;) visual basic
If i understand correctly, this part of '1_5_figazza.php' creates a key too long
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 ?>;
If it is no correct, please, remove the message...
-
Seems to be the problem.
Try changing the `object_manager`column in that table to be of type VARCHAR(50). That should be enough to keep the key below the 1000 bytes.
-
ok, solved with this for an upgrade.
For a new instalation I had modified the file public/install/installation/templates/sql/mysql_schema.php with good result too.
Thanks