[kronolith] Postgres and h3 to h4
Christopher Neuhaus
cne at ruhrverband.de
Wed Mar 28 14:02:07 UTC 2012
Hi List!
I just want to migrate from h3 to 4. Everything works fine but when I
want to update the kronolith db-scheme something goes wrong.
Because I don`t see anything but a exclamation mark at the admin-page, I
use the horde-db-migrate script.
h3 and 4 db encoding is LATIN1.
First turn:
== 6 TurbaUpgradeUpdateSchema: migrated (0.0771s)
=============================
ESC[01;34m[ INFO ] ESC[0mEnding turba schema version: 6
ESC[01;34m[ INFO ] ESC[0mCurrent kronolith schema version: 0
SQLSTATE[42P01]: Undefined table: 7 FEHLER: Relation
<BB>rampage_types<AB> existiert nicht
ZEILE 1: SELECT type_id, type_name FROM "rampage_types" WHERE type_na...
[...]
== 1 HordePrefsBaseTables: migrated (0.0029s)
=================================
Migrating to HordePrefsUpgradeBinaryValue (2)
== 2 HordePrefsUpgradeBinaryValue: migrating
==================================
-- changeColumn('horde_prefs', 'pref_value', 'binary')
SQLSTATE[22P02]: Invalid text representation: 7 FEHLER: ung<FC>ltige
Eingabesyntax f<FC>r Typ bytea
ESC[01;34m[ INFO ] ESC[0mCurrent horde_sessionhandler schema version: 0
Migrating to HordeSessionhandlerBaseTables (1)
Second run:
Migrating to KronolithUpgradeCategoriesToTags (18)
== 18 KronolithUpgradeCategoriesToTags: migrating
=============================
== 18 KronolithUpgradeCategoriesToTags: Migrating event categories to
tags. ===
-- select('SELECT event_uid, event_category, event_creator_id,
calendar_id FROM kronolith_events')
-> 1.9524s
== 18 KronolithUpgradeCategoriesToTags: Unable to find Share: user1
Skipping. ===
== 18 KronolithUpgradeCategoriesToTags: Unable to find Share: user2
Skipping. ===
== 18 KronolithUpgradeCategoriesToTags: Unable to find Share: user3
Skipping. ===
.... and so on
== 18 KronolithUpgradeCategoriesToTags: Unable to find Share: user123
Skipping. ===
== 18 KronolithUpgradeCategoriesToTags: Event categories successfully
migrated.
-- removeColumn('kronolith_events', 'event_category')
-> 0.0051s
== 18 KronolithUpgradeCategoriesToTags: migrated (4309.9885s)
=================
[...]
Migrating to HordePrefsUpgradeBinaryValue (2)
== 2 HordePrefsUpgradeBinaryValue: migrating
==================================
-- changeColumn('horde_prefs', 'pref_value', 'binary')
SQLSTATE[22P02]: Invalid text representation: 7 FEHLER: ung�ltige
Eingabesyntax f�r Typ bytea
Is there an incompatibility to the LATIN1 encoding?
The statement in scripts/upgrades/2009-04-13_horde_pgsql_upgrade.sql
does not work and all other attempts like
http://bytes.com/topic/postgresql/answers/174532-cast-text-bytea just
produce errors.
Best Regards
Christopher
More information about the kronolith
mailing list