Barry,
On Thu, 02 Aug 2001 22:59:11 -0700, you wrote:
>Now in the long run, I would even like to change
>getBlob()/setBlob()/getClob()/setClob() methods to no longer support the
>old large object functionality of postgresql but to move these to
>support a 'toast' version of large objects (once the corresponding
>access methods to toasted columns exist so that toasted columns can
>really be treated as large objects).
Could you elaborate on that please? What new access methods are
needed on toasted columns? Does this require backend support?
FE/BE protocol changes?
Would it be conceivable to implement the Lob JDBC interface on
the current implementation of toasted columns (in both the
backend and the protocol), e.g. using a OID/column name pair as
the "logical pointer" needed by JDBC?
Also, I'm wondering if it would be wise to re-architect Lob
support in the JDBC interface only? Someone creating a Lob
through JDBC may have a hard time accessing his data using
another interface that not yet supports efficient access methods
on huge toasted data. I definitely agree Blob->toast is the most
desirable mapping from a JDBC point of view, but I'm not sure if
this should be changed only in JDBC.
Regards,
René Pijlman
