Re: BLOBs etc

From: Kris Jurka <books(at)ejurka(dot)com>
To: Thomas Hallgren <thhal(at)mailblocks(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: BLOBs etc
Date: 2005-01-07 20:03:13
Message-ID: Pine.BSO.4.56.0501071500280.11678@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Fri, 7 Jan 2005, Thomas Hallgren wrote:

> Kris
> > I'm not clear what your advocating in concrete terms. A new pseudo type
> > "binary data" that could be used until it needs to convert it into a
> > concrete type? When does this conversion have to happen?
> >
> Couldn't this be limited to the client/server protocol? There are 4
> cases that will fail today. If you attempt to:
>
> 1. stream lob data from the client for storage in a bytea.
> 2. send a bytea data "by value" for storage in a LOB.
> 3. read LOB data that is passed as a bytea.
> 4. read bytea data that is really a LOB.
>
> As you pointed out earlier, it should be possible to make the client
> handle cases #3 and #4 so what's left for the server is to deal with #1
> and #2. That doesn't sound like rocket science to me.
>

Well you've summarized the problem, but you certainly haven't given any
concrete suggestions on how this could actually be done. I'm not sure
this even qualifies as handwaving.

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Keith Hankin 2005-01-07 20:39:16 Re: One byte integer support
Previous Message Thomas Hallgren 2005-01-07 16:55:06 Re: BLOBs etc