Re: BLOBs etc
От
Kris Jurka
Тема
Re: BLOBs etc
Дата
Msg-id
Pine.BSO.4.56.0501071500280.11678@leary.csoft.net
Ответ на
Re: BLOBs etc (Thomas Hallgren)
Список
Дерево обсуждения
BLOBs etc Sven Köhler <skoehler@upb.de>
Re: BLOBs etc Oliver Jowett <oliver@opencloud.com>
Re: BLOBs etc Kris Jurka <books@ejurka.com>
Re: BLOBs etc Sven Köhler <skoehler@upb.de>
Re: BLOBs etc Kris Jurka <books@ejurka.com>
Re: BLOBs etc Sven Köhler <skoehler@upb.de>
Re: BLOBs etc Kris Jurka <books@ejurka.com>
Re: BLOBs etc Sven Köhler <skoehler@upb.de>
Re: BLOBs etc Kris Jurka <books@ejurka.com>
Re: BLOBs etc Sven Köhler <skoehler@upb.de>
Re: BLOBs etc Kris Jurka <books@ejurka.com>
Re: BLOBs etc Thomas Hallgren <thhal@mailblocks.com>
Re: BLOBs etc Oliver Jowett <oliver@opencloud.com>
Re: BLOBs etc Thomas Hallgren <thhal@mailblocks.com>
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
В списке pgsql-jdbc по дате отправления