On 2 Oct 2003, Doug McNaught wrote:
> Howard Lowndes <[EMAIL PROTECTED]> writes:
>
> > OK, I'm convinced, except for one small, but not insignificant hiccup.
> > When you dump a database with the BLOBs, even with the -c option, and then
> > restore that databas
On Thu, 2 Oct 2003, Tom Lane wrote:
> Howard Lowndes <[EMAIL PROTECTED]> writes:
> > On Wed, 1 Oct 2003, Tom Lane wrote:
> >> No, because pg_restore has logic to adjust the references to match the
> >> new BLOB OIDs. If you have a test case where this
On Wed, 1 Oct 2003, Tom Lane wrote:
> Howard Lowndes <[EMAIL PROTECTED]> writes:
> > Now, my concern is that if I use pg_dump with the --clean or --create, and
> > the --blobs options, and then try a pg_restore from the resulting archive
> > file, I believe the BLO
lost by reason of a pg_dump -c -b and a subsequent pg_restore causing the
BLOBs to locate into different loids.
Is there some way of constraining loid in images to ID in Large Objects?
>
>
> Howard Lowndes wrote:
>
> >My situation is that I am interacting PHP 4.1.2 to PostgreSQL
My situation is that I am interacting PHP 4.1.2 to PostgreSQL 7.2.2
I have no difficulty inserting and managing BLOBs into the Large Object
system table, and I have a user table called images which maintains the
relationship between the BLOB loid and the identity that relates to it in
my user t
On Mon, 22 Sep 2003, Tom Lane wrote:
> Howard Lowndes <[EMAIL PROTECTED]> writes:
> > I'm working psql v7.2.2 to postmaster v7.2.2 and want to use the
> > \lo_import function.
> > The psql manual says that the syntax is \lo_import '' 'comment'
