[#1781] Turba lacks PostgreSQL upgrade script
Summary Turba lacks PostgreSQL upgrade script
Queue Turba
Queue Version 2.0.2
Type Bug
State Resolved
Priority 1. Low
Owners
Requester lexicon (at) seul (dot) org
Created 04/13/2005 (1365 days ago)
Due
Updated 04/13/2005 (1365 days ago)
Assigned
Resolved 04/13/2005 (1365 days ago)
Attachments 1.2_to_2.0.pgsql[1].sql Download
1.2_to_2.0.pgsql.sql Download
1.2_to_2.0.sql Download
Milestone
Patch No

History
04/13/2005 Chuck Hagenbuch Comment #5
State ⇒ Resolved
Reply to this comment
The generic upgrade script has been committed, thanks.
04/13/2005 Chuck Hagenbuch Comment #4 Reply to this comment
No new scripts are needed for object_type and object_members; you just 
need to read docs/UPGRADING:

.. Important:: These upgrade instructions assume that you are upgrading from
                at least Turba 1.2.  If you have an older version of Turba,
                follow the 'upgrade steps'_ described in Turba 1.2 or higher
                first.

.. _'upgrade steps': 
http://cvs.horde.org/annotate.php/turba/docs/Attic/UPDATE?sa=1&rev=1.1.2.6

04/13/2005 lexicon (at) seul (dot) org Comment #3
New Attachment: 1.2_to_2.0.pgsql[1].sql Download
Reply to this comment
One of the categories, object_type, is not correctly updated by the 
current scripts.  This object type will require new, separate scripts, 
to support each db type (since this one cannot be added by one 
consolidated version).

Also missing from the upgrade script is object_members, which is added 
in this script.

Attached is the postgres version.
04/13/2005 lexicon (at) seul (dot) org Comment #2
New Attachment: 1.2_to_2.0.sql Download
Reply to this comment
General upgrade script for MySQL / PostgreSQL.
04/13/2005 lexicon (at) seul (dot) org Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Turba lacks PostgreSQL upgrade script
Queue ⇒ Turba
New Attachment: 1.2_to_2.0.pgsql.sql Download
Reply to this comment
Turba lacks a PostgreSQL upgrade script.  However, the PostgreSQL 
version doesn't require any changes from the MySQL one to actually 
run.  The filename and instructions do not reflect this, however.   
Either the attached pgsql one should be added for consistency, or the 
attached general one (which I will attach in the next comment) should 
replace the existing MySQL-specific version.