Can this be added to the TODO list? (actually put back on the TODO list)
Along with this email thread?
I feel that it is very important to have BLOB support in postgres that
is similar to what the commercial databases provide. This could either
mean fixing the current implementation or adding
Jan Wieck <[EMAIL PROTECTED]> writes:
> For all the default operations, the system would treat the
> datums still like regular attributes. That means, that an
> INSERT ... SELECT ...
> copying a BLOB from one table to another (and that's correct,
> BLOB's should have
I wrote:
> Tom Lane wrote:
> >
> > Implementation is left as an exercise for the reader ;-).
> >
> > Offhand this seems like it would be doable for a column-value that
> > was actually moved out-of-line by TOAST, since the open_toast_object
> > function could see and return the TOAST pointer, and
Tom Lane wrote:
>
> Jan Wieck <[EMAIL PROTECTED]> writes:
> > One of the problems I saw, and that's probably why we don't
> > have a proposal yet, is, that the size of the data is
> > recorded in the toast reference held in the main tuple. If
> > you later open the to
Jan Wieck <[EMAIL PROTECTED]> writes:
> One of the problems I saw, and that's probably why we don't
> have a proposal yet, is, that the size of the data is
> recorded in the toast reference held in the main tuple. If
> you later open the toast value for writing, you'll
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I keep bugging Jan about it, since pre-7.1 and no one has come up with
> > an idea.
>
> Well, if you want an idea:
>
>BEGIN;
>
>SELECT open_toast_object(toastable_column) FROM tab WHERE ...;
>
>-- app checks that it got ex
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I agree we should have it, but I thought the problem was that we
> > couldn't come up with an API that worked.
>
> AFAIR, no one's really tried yet. I do not recall any proposals
> getting shot down ...
One of the problems I s
Tom Lane wrote:
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I keep bugging Jan about it, since pre-7.1 and no one has come up with
> > an idea.
>
> Well, if you want an idea:
>
> BEGIN;
>
> SELECT open_toast_object(toastable_column) FROM tab WHERE ...;
>
> -- app
Bruce Momjian wrote:
>
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > I agree we should have it, but I thought the problem was that we
> > > couldn't come up with an API that worked.
> >
> > AFAIR, no one's really tried yet. I do not recall any proposals
> > getting shot down ...
>
> I kee
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Offhand this seems like it would be doable for a column-value that
>> was actually moved out-of-line by TOAST, since the open_toast_object
>> function could see and return the TOAST pointer, and then the read/
>> write operations just hack on rows in pg
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I keep bugging Jan about it, since pre-7.1 and no one has come up with
> > an idea.
>
> Well, if you want an idea:
>
> BEGIN;
>
> SELECT open_toast_object(toastable_column) FROM tab WHERE ...;
>
> -- app checks that it got exact
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I keep bugging Jan about it, since pre-7.1 and no one has come up with
> an idea.
Well, if you want an idea:
BEGIN;
SELECT open_toast_object(toastable_column) FROM tab WHERE ...;
-- app checks that it got exactly one result ba
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I agree we should have it, but I thought the problem was that we
> > couldn't come up with an API that worked.
>
> AFAIR, no one's really tried yet. I do not recall any proposals
> getting shot down ...
I keep bugging Jan about it, since pre-7.1 a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I agree we should have it, but I thought the problem was that we
> couldn't come up with an API that worked.
AFAIR, no one's really tried yet. I do not recall any proposals
getting shot down ...
regards, tom lane
-
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> By 'in/out interface for TOAST columns' I thought this item dealt with
> >> adding large object like functions to read/write/append to TOAST column
> >> data. I know that has been talked about in the past on hackers. But I
> >> don't see it on
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> By 'in/out interface for TOAST columns' I thought this item dealt with
>> adding large object like functions to read/write/append to TOAST column
>> data. I know that has been talked about in the past on hackers. But I
>> don't see it on the todo l
> OK. Those functions are in the docs. I didn't relate those functions
> and this todo item together.
>
> By 'in/out interface for TOAST columns' I thought this item dealt with
> adding large object like functions to read/write/append to TOAST column
> data. I know that has been talked abou
OK. Those functions are in the docs. I didn't relate those functions
and this todo item together.
By 'in/out interface for TOAST columns' I thought this item dealt with
adding large object like functions to read/write/append to TOAST column
data. I know that has been talked about in the pas
> I was going through the Todo list looking at the items that are planned
> for 7.2 (i.e. those starting with a '-'). I was doing this to see if
> any might impact the jdbc driver. The only one that I thought might
> have an impact on the jdbc code is the item:
>
> * -Make binary/file in/ou
I was going through the Todo list looking at the items that are planned
for 7.2 (i.e. those starting with a '-'). I was doing this to see if
any might impact the jdbc driver. The only one that I thought might
have an impact on the jdbc code is the item:
* -Make binary/file in/out interface
20 matches
Mail list logo
