Sender: wn@kja-essen.de
Message-ID: <37F62F39.CF77422E@kja-essen.de>
Date: Sat, 02 Oct 1999 18:13:45 +0200
From: Wolfgang Hottgenroth <wn@kja-essen.de>
Reply-To: woho@ieee.org
MIME-Version: 1.0
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
CC: woho@ieee.org, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] problems with large-objects
References: <1665.938878406@sss.pgh.pa.us> <37F62682.D3A869EA@kja-essen.de>
	<37F62DE3.A78CD73A@alumni.caltech.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi again,


Thomas Lockhart wrote:
> 
> > So I failed when reading the manual,
> > because I never realized, that using transactions are a requirement when
> > working with LO's.
> > > This restriction has been documented as required all along,
> 
> Well, just because we think we've documented it doesn't mean that it
> is obvious. Now that you know, do the docs you were reading make this
> clear and you just missed it, or should it be mentioned in more places
> than it is currently? Let us know if you have suggestions for
> improvements...

Of course I take an immediate look into the docs, and I found it: In the
sample program of the Large-Object-chapter (Chapter 15). Is this the
only place where it is documented? If this is the only place, then I
think, it should be mentioned in more places. Or can you tell me, where
I can read more about it?


Wolfgang