Received: from cr322781-a.ym1.on.wave.home.com (cr322781-a.ym1.on.wave.home.com [24.112.37.89]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0C46Op81578 for ; Thu, 11 Jan 2001 23:06:24 -0500 (EST) (envelope-from svanegmond@bang.dhs.org) Received: from svanegmond by cr322781-a.ym1.on.wave.home.com with local (Exim 3.20 #1 (Debian)) id 14GvXU-0008KQ-00; Thu, 11 Jan 2001 23:10:08 -0500 Date: Thu, 11 Jan 2001 23:10:08 -0500 To: Louis Bertrand Cc: pgsql-php@postgresql.org Subject: Re: pg_loopen() error Message-ID: <20010111231007.A32006@bang.dhs.org> Reply-To: svanegmond@home.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from louis@bertrandtech.on.ca on Thu, Jan 11, 2001 at 11:17:22PM -0500 From: Stephen van Egmond X-Archive-Number: 200101/49 X-Sequence-Number: 114 Louis Bertrand (louis@bertrandtech.on.ca) wrote: > Any clues? Known bug in pg_loopen? Pilot error? I think large objects need to be read in a begin/end block. The annotated PHP covers this in the user comments...