Closed (cannot reproduce)
Project:
BeautyTips
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jul 2011 at 00:05 UTC
Updated:
9 Feb 2018 at 20:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kleinmp commentedThis update is for people who have already been using the beayttips manager. I modified the update in the dev version so it takes this into account.
Comment #2
alphasupremicus commentedI had the same error when applying update 7000. I run a PostgreSQL back-end and the update 7000 has some MySQL-specific syntax in the update. Attached is a patch that uses the Drupal DB Abstraction layer API that should accomplish this regardless of what database flavor you are using. Cheers!
Comment #3
kleinmp commentedThanks for the patch! I added this to the dev version, and will probably release a new alpha version today for this and some other bug fixes.
Comment #5
philsward commentedI hate to re-open a "fixed" issue, but I just tried an upgrade from the latest D6 dev to beta2 and I received the same error even with the included patch installed... I have no idea how to fix it either :-/
Comment #6
philsward commentedAlso getting similar for #7002 but it might be related to me manually adding a "beautytips_custom_tips" table in the DB without actually knowing what I'm doing...
Failed: DatabaseSchemaObjectDoesNotExistException: Cannot change the definition of field beautytips_custom_tips.element: field doesn't exist. in DatabaseSchema_mysql->changeField() (line 454 of /home/user/public_html/t/upgrade/includes/database/mysql/schema.inc).
Update: Managed to get past the errors by manually creating the db columns... No idea if I have them setup right though. I'm using MySQL 5.5 and I'm wondering if the update process is designed for earlier versions?
Comment #7
pifagor commented