[OGo-Users] NOTICE: OGo incompatible with PostgreSQL 8.3

[Adam Tauno Williams]

--=-e5hzgoZNRCBz/1AYclyN
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Due to changes in PostgreSQL 8.3 current OGo instances will break.  This
is the result of 8.3 no longer performing automatic casting of INT to
TEXT when INTs are compared to character types.
<http://www.postgresql.org/docs/8.3/static/release-8-3.html>  Since OGo
generates a query that compares an integer to a string during ACL
processing this will produce a database exception.

A simple work around is to perform -
ALTER TABLE object_acl=20
  ALTER COLUMN object_id TYPE INT USING  object_id::int;
ALTER TABLE object_acl=20
  ALTER COLUMN auth_id   TYPE INT USING  auth_id::int;
 - after updating PostgreSQL.  Then OGo should continue to work
normally;  OGo doesn't actually required the auth_id or object_id values
in the object_acl table to be strings (you should only find integer
values in those columns).

!!!ALWAYS BACKUP YOUR DATABASE BEFORE MAKING ANY MANUAL CHANGES!!!

See the thread at
<http://mail.opengroupware.org/pipermail/developer/2008-February/003434.htm=
l> for more information.

!!!ALWAYS BACKUP YOUR DATABASE BEFORE MAKING ANY MANUAL CHANGES!!!

See either the pg_dump manual page or the PostgreSQL chapter of WMOGAG
<http://docs.opengroupware.org/Members/whitemice/wmogag/file_view> for
information on backup up the OGo database.   And if you need this advice
then you probably aren't backup up regularly already...

--=-e5hzgoZNRCBz/1AYclyN
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHuaydLRePpNle04MRAghpAJ9fvVTjGfLs9WYb5G3r5a+dLCZDtQCfWl+T
t0EAGfK6AOXKd3kQzko+huI=
=IlAS
-----END PGP SIGNATURE-----

--=-e5hzgoZNRCBz/1AYclyN--