Forum OpenACS Q&A: OACS 3.2.5 on Postgres 7.2

Collapse
2: OACS 3.2.5 on Postgres 7.2 (response to 1)
Posted by Jonathan Ellis on
I asked this question a couple days ago and got no response. Here's what I see from searching the bboard:
char/varchar problems:
bboard: https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0004g2
bboard: https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0004uD
sec_: https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=00041d
(also: https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0003tm)
(this is the problem you ran into, and suggests a better solution)
null abuse:
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0004Sy

general, including non-db fixes to 3.2.5:
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0003ze

So we have at least 6 people running 3.2.5 on PG 7.2, who have reported around half a dozen "core" errors. You'll probably see more in parts of the toolkit these people haven't explored, but it doesn't look unmanagable by any means.