[Zope] Problems with Zope and SQL methods

[Federico Di Gregorio]

Hi,

    some people have solved the problem you have simply switching to
psycopg. the psycopg type-system, apart from being fully customizable,
treat the oid type the correct way, returning an integer. on the other
side you don't get automatic management of lob (that popy does) but with
7.1 and unlimited row size less and less people use lobs anymore. (and,
imho, there is no way to access lobs trasparently without getting into
the oid problem in postgres.)

    anyway, you'll find psycopg at http://initd.org/Software/psycopg/

ciao,
federico

----------  Forwarded Message  ----------
Subject: [Zope] Problems with Zope and SQL methods
Date: Sun, 3 Jun 2001 15:00:48 +0100
From: "Neil McIntosh" <nmcintosh@sentec.co.uk>
To: <zope@zope.org>


Hello all,

I have recently upgraded and moved a zope server to 2.3.2.  This has
proved
a difficult task as we are using it to access an intranet database
running
on Postgresql back end.  Whenever a query is run where an oid is
returned it
hangs the ZServer and core dumps.

eg
select * from people
OR
select p.oid, p.name from people p

This can be avoided by setting the type as follows.

select p.oid::int, p.name from people p

However the following will still cause a core dump

select p.oid::int, p.* from people p.

I have noticed that others have been having similar problems but not
seen
any solutions on this list.


-- 
Federico Di Gregorio
MIXAD LIVE Chief of Research & Technology              fog@mixadlive.com
Debian GNU/Linux Developer & Italian Press Contact        fog@debian.org
                             Best friends are often failed lovers. -- Me