[horde] H3 to H5 upgrade - some database structure differences

[Geoff Roberts]

Hi,

I'm testing an upgrade from Horde 3 to Horde 5.

Read the UPGRADING and INSTALL notes.

After upgrading I found some differences between the upgraded Horde 3 database 
and a vanilla Horde 5 database.

Just wanted to check if these are expected with someone in the know...

1. Some potential items not adjusted

a) in horde_signups
signup_date was left as varchar(255) and not converted to int(11)

Looking at the code in Horde 5, it assumes Unix epoch time (hence the int(11)) 
so this difference could cause grief.

b) in horde_alarms
Horde 5 has a new 'id' column which is an autoincrement
This was not created in the upgraded Horde 3 database.

Other differences when between Horde 3 upgraded and vanilla Horde 5 - would any 
of these make any difference?

a) A few longblob not converted to blob
b) A few bigint not converted to int
c) A few varchar(250 or 200) not converted to varchar(255)
d) Some tinyint not converted to smallint
e) A tinyint not converted to int
f) A whole range of indexes were not renamed - eg in horde_alarms
  KEY `alarm_id_idx` (`alarm_id`) was not renamed to   KEY 
`index_horde_alarms_on_alarm_id` (`alarm_id`)

Kind regards,

Geoff