MySql-problems when downgrading from 3.5aplha1 to 3.4.2

Previous topic

Setup & design

Next topic

Author	Message
Felix Laate	Friday 15 October 2004 2:24:31 am Hi all! When downgrading from 3.5aplha1 to 3.4.2 (why not!) and checking for database-consistecy, I get a list of things I need to fix. I can fix em all, except for two, which give this output: <i> mysql> ALTER TABLE ezcontentobject_tree ADD INDEX ezcontentobject_tree_path_ident ( path_identification_string ); ERROR 1170: BLOB column 'path_identification_string' used in key specification without a key length mysql> mysql> ALTER TABLE ezurl_object_link DROP INDEX PRIMARY; ERROR 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 'PRIMARY' at line 1 </i> Any ideas, anybody? Felix Publlic Relations Manager Greater Stavanger www.greaterstavanger.com
Conor Murray	Friday 05 November 2004 9:43:06 am A bit late... but I saw the first error today when upgrading to 3.4.2 - the fix is to specify a size (50 seems to be the correct size), thus: ALTER TABLE ezcontentobject_tree ADD INDEX ezcontentobject_tree_path_ident ( path_identification_string (50)); The second one appears to be an erroneously generated statement to attempt to drop a primary index... you probably need to substitute in the NAME of the primary index for the particular table. Approach with care! Language is a virus - William S Burroughs

Author

Message

Felix Laate

Friday 15 October 2004 2:24:31 am

Hi all!

When downgrading from 3.5aplha1 to 3.4.2 (why not!) and checking for database-consistecy, I get a list of things I need to fix. I can fix em all, except for two, which give this output:

<i>
mysql> ALTER TABLE ezcontentobject_tree ADD INDEX ezcontentobject_tree_path_ident ( path_identification_string );
ERROR 1170: BLOB column 'path_identification_string' used in key specification without a key length
mysql>

mysql> ALTER TABLE ezurl_object_link DROP INDEX PRIMARY;
ERROR 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 'PRIMARY' at line 1
</i>

Any ideas, anybody?

Felix

Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com

Conor Murray

Friday 05 November 2004 9:43:06 am

A bit late... but I saw the first error today when upgrading to 3.4.2 - the fix is to specify a size (50 seems to be the correct size), thus:

ALTER TABLE ezcontentobject_tree ADD INDEX ezcontentobject_tree_path_ident ( path_identification_string (50));

The second one appears to be an erroneously generated statement to attempt to drop a primary index... you probably need to substitute in the NAME of the primary index for the particular table. Approach with care!

Language is a virus - William S Burroughs