Doesn't seem to have had any adverse effects but did see these errors when upgrading a test site from 2.2 to 3.0beta1
ALTER TABLE tiki_users_score CHANGE event_id event_id char(200) NOT NULL default ''
Specified key was too long; max key length is 1000 bytes
ALTER TABLE tiki_users_score ADD PRIMARY KEY 110),event_id(110
Incorrect sub part key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique sub keys
ALTER TABLE tiki_users_score ADD KEY user (user(110),event_id(110),expire)
Incorrect sub part key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique sub keys
INSERT INTO users_permissions (permName, permDesc, level, type) VALUES ('tiki_p_search_categorized', 'Can search on objects of this category', 'basic', 'category')
Duplicate entry 'tiki_p_search_categorized' for key 1
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |