| From: | Andreas Prohaska <ap(at)apeiron(dot)de> |
|---|---|
| To: | "'pgsql-jdbc(at)postgresql(dot)org'" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Streaming binary data into db, difference between Blob |
| Date: | 2003-09-10 14:25:39 |
| Message-ID: | A11D9B8C48C1D411AE0C000062A129947B1C68@ganymed.allocation.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Ahh, I don't know if that's a good idea.
Perhaps I didn't get you right, but this means that while
you can access your blobs with c-jdbc without problems, you
can no longer access them NOT using c-jdbc, because this would
require simulating the logical blob manager.
> That sounds like really good idea.
>
> Just we can't map to bytea cause it is specific to Postgres,
> but I would
> definitely put this on the feature list for c-jdbc.
>
> Thanks a lot for that.
>
> Nicolas,
>
> On Wed, 2003-09-10 at 16:14, Dave Tenny wrote:
> > You could always implement your own logical blob manager that
> > implements blob IDs
> > and breaks blobs into BYTEA records of a particular (manageable)
> > maximum size and associates
> > multiple BYTEA chunks with the blob id.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Tenny | 2003-09-10 14:27:46 | Re: Streaming binary data into db, difference between Blob |
| Previous Message | Fernando Nasser | 2003-09-10 14:20:04 | Re: Streaming binary data into db, difference between Blob |