From: Tom Lane <tgl@sss.pgh.pa.us>
To: dougt@mugc.cc.monash.edu.au
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Problems with postgres V6.5.3 large objects
Date: Mon, 06 Dec 1999 11:07:56 -0500
Message-ID: <18743.944496476@sss.pgh.pa.us> (raw)
In-Reply-To: <199912060935.UAA28036@mugca.cc.monash.edu.au>
Douglas Thomson <dougt@mugc.cc.monash.edu.au> writes:
>> Most of the developers have not wanted to put much effort into large
>> objects, since where we really want to go is to eliminate tuple size
>> restrictions; once that happens large objects will be much less
>> necessary.
> I am curious about the planned interface once tuple size restrictions
> are eliminated. I am using large objects, and want to make my
> application port as painlessly as possible.
This hasn't been thought about much, AFAIK. I agree that with large
fields in tuples, it'd be nice to have operations that read or write
portions of fields, and also ways to read/write binary data without any
encoding. But I'm not real sure what the API should look like. Are
there precedents in other DBMSes?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, dougt@mugc.cc.monash.edu.au
Subject: Re: [INTERFACES] Problems with postgres V6.5.3 large objects
In-Reply-To: <18743.944496476@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox