upgrade/update-database.php: v2.3.5: DB Error

Bug #1273540 reported by Brian LaVallee
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Eventum
Fix Released
Medium
Elan Ruusamäe

Bug Description

I ran into the following while upgrading from 2.3.3 to 2.3.5

Turns out that "eventum_" was hard-coded instead of using %TABLE_PREFIX%
It's just two lines, easy enough to fix with sed, but diff is attached.

[root@eventum upgrade]# ./update-database.php
* Applying patch: 12 (12_timetracking_project.sql)
DB Error: no such table: -- select first project id - we keep this as default
select prj_id from eventum_project limit 1 into @prj_id [nativecode=1146 ** Table 'eventumdev.eventum_project' doesn't exist]
[root@eventum upgrade]#

[root@eventum upgrade]# ./update-database.php
* Applying patch: 12 (12_timetracking_project.sql)
DB Error: unknown error: ALTER TABLE time_tracking_category
 ADD COLUMN ttc_prj_id int(10) unsigned NOT NULL default 0 after ttc_id,
 DROP KEY ttc_title,
 ADD KEY ttc_title (ttc_prj_id, ttc_title) [nativecode=1060 ** Duplicate column name 'ttc_prj_id']
[root@eventum upgrade]#

Revision history for this message
Brian LaVallee (b-lavallee) wrote :
Revision history for this message
Elan Ruusamäe (glen666) wrote :

fix included in 2.3.6 release

Changed in eventum:
milestone: none → 2.3.6
assignee: nobody → Elan Ruusamäe (glen666)
importance: Undecided → Medium
status: New → Fix Released
tags: removed: 2.3.3 2.3.5 upgrade
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.