[OGo-Users] Postgre fatal error after new install on Suse 10.2

[Adam Tauno Williams]

> > Hey at least you can reproduce it.  Something broken in Suse 10.2  
> > version of
> > PostgreSQL I assume.
> Hm, no, I don't think anything is broken in _PostgreSQL_. Our usage  
> of the PG API might be incorrect (why is it treated as a string,  
> probably there is a better way?).
> Anyways, probably the locale changed and the datetime format changed  
> in the same run, leading to the issue. I _think_ the datetime format  
> can be set using some environment variable, but I'm not perfectly sure.

Yes, there are both the PGDATESTYLE and PGTZ environment variables;  as
well as the PGCLIENTENCODING which I suppose could be involved.

There are also equivalent SET command; "SET datestyle TO ..." and "SET
timezone TO ...".

I think what OGo/SOPE wants is:
SET datestyle TO ISO;  // YYYY-MM-DD HH:MM:SS
SET timezone To 'GMT'; // Set the DBs timezone to GMT

Perhaps it would be a good idea to execute these two commands when
SOPE/OGo sets up its database connection,  this might work around if the
systems defaults are funky.

In the short term I'll try making sure these are set in OGo's
environment and see what happens.