| Summary | DB-Upgrade error message postgres - pref_value cannot be casted to bytea |
| Queue | Horde Base |
| Queue Version | 4.0.13 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | tkrah (at) fachschaft (dot) imn (dot) htwk-leipzig (dot) de |
| Created | 12/22/2011 (4896 days ago) |
| Due | 12/23/2011 (4895 days ago) |
| Updated | 02/01/2012 (4855 days ago) |
| Assigned | 01/03/2012 (4884 days ago) |
| Resolved | 01/31/2012 (4856 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
Horde_Db_Adapter_Postgresql_Schema::changeColumn() to manually cast
the values if altering a column type doesn't work automatically. The
error is logged though before we catch it, that's why it shows up in
the logs.
1. How do i test if those values are migrated correctly, e.g. where to
look for?
2. How to run those tests, is there some doc where i can start to
provide you with those informations?
thx.
Priority ⇒ 2. Medium
State ⇒ Feedback
explicitly have a unit test that tests this migration and that runs
fine with the Postgres versions and test data at our hands.
Please run the tests on your system and report back the results.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ DB-Upgrade error message postgres - pref_value cannot be casted to bytea
Due ⇒ 12/23/2011
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Horde told me all went fine, however, in the logs i did found this -
don't know if this one is serious:
Dec 22 21:45:09 mail HORDE: [horde] SQL QUERY FAILED: SQLSTATE[42804]:
Datatype mismatch: 7 ERROR: column "pref_value" cannot be cast to
type bytea
#012#011ALTER TABLE "horde_prefs" ALTER COLUMN"pref_value" TYPE bytea [pid 14585 on line 812 of
"/usr/share/php/Horde/Db/Adapter/Base.php"]
Can this one be ignored? If not, how to fix this error or my database?