[horde] Creating horde_prefs manually...

[Ralf Lang]

On 15.01.2015 06:13, Michael Robinson wrote:
> I shouldn't have to do this, but I gave it a shot.
> 
> mysql> SELECT * FROM horde_prefs;
> +-----------------+----------------------+----------+------------+
> | pref_name       | pref_value           | pref_uid | pref_scope |
> +-----------------+----------------------+----------+------------+
> | identities      | a:1:{i:0;a:4:{s:2:"i | admin    | horde      |
> | upgrade_tasks   | a:3:{s:5:"horde";s:5 | admin    | horde      |
> | last_logintasks | a:2:{s:5:"horde";i:1 | admin    | horde      |
> | last_login      | a:2:{s:4:"host";s:25 | admin    | horde      |
> | upgrade_tasks   | a:3:{s:5:"horde";s:5 | michael  | horde      |
> | last_login      | a:2:{s:4:"host";s:25 | michael  | horde      |
> | last_logintasks | a:2:{s:5:"horde";i:1 | michael  | horde      |
> | identities      | a:1:{i:0;a:4:{s:2:"i | michael  | horde      |
> | upgrade_tasks   | a:3:{s:5:"horde";s:5 | mom      | horde      |
> | last_login      | a:2:{s:4:"host";s:25 | mom      | horde      |
> | last_logintasks | a:2:{s:5:"horde";i:1 | mom      | horde      |
> | identities      | a:0:{}               | mom      | horde      |
> +-----------------+----------------------+----------+------------+
> 12 rows in set (0.00 sec)
> 
> mysql> 
> 
> I read error messages from horde about table columns not existing and
> created them using an educated guess on field type.  I guessed that each
> column should be a varchar(20), but that is probably wrong. 
No wonder it's not working. pref_value needs to be defined as longblob,
not as varchar(20).

It stores very long json strings.


 Horde is
> still failing to read the preferences back when I log back in.  Uge!
> Clearly horde has saved preferences, but it isn't reading them back.

Because it's broken data in a broken table format.

> I'm also concerned that I should never have had to create this table
> manually.  Now that I know more about the table format, I could try
> creating the table in postgresql and avoid having to use two databases.

You should fix the original issue.

horde-db-migrate Horde_Prefs down
horde-db-migrate Horde_Prefs up



-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang at b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.horde.org/archives/horde/attachments/20150115/d03f3f89/attachment.bin>