This is the case at the moment anyway. The problem is that each database
is encoding its own way long strings of data.
It is not the same encoding from postgres as it is with mysql, as it
with hypersql or other databases.
We have chosen to encode data a way that is supported by all databases,
and indeed you can't read the blobs again if you're not using c-jdbc
anymore.
But if we don't go this approach then I don't how we can support
heterogeneous clusters of databases.
At the moment, we are also trying to implement streaming of data only if
the underlying driver supports streaming.
Please, share with us ideas on the c-jdbc mailing list if you have the
time. Critics are welcomed.
Nicolas,
On Wed, 2003-09-10 at 16:25, Andreas Prohaska wrote:
> 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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>