=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmog...@softperience.eu> writes:
> Tom Lane <t...@sss.pgh.pa.us> Thursday 02 of June 2011 16:42:42
>> Yes. I think the appropriate problem statement is "provide streaming
>> access to large field values, as an alternative to just fetching/storing
>> the entire value at once". I see no good reason to import the entire
>> messy notion of LOBS/CLOBS. (The fact that other databases have done it
>> is not a good reason.)
> In context of LOBs streaming is resolved... I use current LO functionallity
> (so driver may be able to read LOBs as psql \lo_export does it or using COPY
> subprotocol) and client should get just LO's id.
Just to be clear: I do not want to expose a concept of object IDs for
field values in the first place. All of the problems you enumerate stem
from the idea that LOBs ought to be a distinct kind of field, and I
don't buy that.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
