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
You must be logged in to post messages in this topic!