6.0.0-beta1
7/21/25

[#3423] Upgrade script from 1.2 to 2.0 fails
Summary Upgrade script from 1.2 to 2.0 fails
Queue Turba
Queue Version 2.0.5
Type Bug
State Not A Bug
Priority 3. High
Owners
Requester keith (at) ajmani (dot) org
Created 02/08/2006 (7103 days ago)
Due
Updated 02/08/2006 (7103 days ago)
Assigned
Resolved 02/08/2006 (7103 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/08/2006 04:36:19 PM keith (at) ajmani (dot) org Comment #5 Reply to this comment
Fair enough -- must be a debian bug then, in that they failed to pick 
up or run that upgrade.



Many thanks for the diligence. I'm happy that my horde3/turba2 system 
is up and running fine now.



Keith
02/08/2006 02:16:36 PM keith (at) ajmani (dot) org Comment #3 Reply to this comment
Hi:



Like I said in the bug, I was upgrading from 1.2. And there is no doubt that:

a) contacts were working with turba

b) contacts did not work after the upgrade



if you would like a CVS version number from a particular file, please 
let me know and I will post it.



boe:/usr/share/horde2/turba# dpkg -l turba

Desired=Unknown/Install/Remove/Purge/Hold

| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed

|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)

||/ Name           Version        Description

+++-==============-==============-============================================

ii  turba          1.2.5-3        A web based contact manager






02/08/2006 05:32:03 AM Chuck Hagenbuch Comment #2
State ⇒ Not A Bug
Reply to this comment
object_type and object_members were added in 1.2. It is explictly 
documented that you _must_ upgrade from 1.2, not from an earlier 
version.
02/08/2006 12:27:40 AM keith (at) ajmani (dot) org Comment #1
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Upgrade script from 1.2 to 2.0 fails
Queue ⇒ Turba
Reply to this comment
The upgrade script for 1.2 -> 2.0, included in 
turba2/examples/scripts/upgrades/1.2_to_2.0.sql does not make all the 
necessary changes to an existing database.



The script runs successfully, but upon login users are unable to 
browse the contents of their existing "My Address Book".  Using the 
"Private Address Book" succeeds.



Attempting to add a new record to "My Address Book" fails, with the 
following errors:



on screen: DB Error: no such field



in log:



Feb 07 19:14:27 HORDE [error] [turba] DB Error: no such field: INSERT 
INTO turba

_objects (object_name, object_email, object_alias, object_homeaddress, 
object_wo

rkaddress, object_homephone, object_workphone, object_cellphone, 
object_fax, obj

ect_title, object_company, object_notes, object_pgppublickey, 
object_smimepublic

key, object_freebusyurl, object_type, owner_id, object_uid, object_id) 
VALUES ('

Keith Ajmani3', '', '', '', '', '', '', '', '', '', '', '', '', '', 
'', 'Object'

, 'keith', '20060207191427.6rvgct4txy4g@webmail.skule.net', 
'56f6f8fdd7a6377b03a

824ecbf52c490') [nativecode=1054 ** Unknown column 'object_type' in 
'field list'

] [on line 185 of "/usr/share/horde3/turba/lib/Driver/sql.php"]



I checked the turba_objects DB, and sure enough that field, and also 
'object_members' are missing. I compared the DB fields to the ones in 
the turba create script.



I executed the following SQL and now the address book works!



alter table turba_objects add column object_type VARCHAR(255) NOT NULL 
DEFAULT 'Object';

alter table turba_objects add column object_members BLOB;



Please update the upgrade script.



Thank you,



Keith




Saved Queries