Gunnar,
bytea is an escaped variable length binary datatype.
bytea | variable-length string, binary values escaped
It should work with postgreSQL versions greater than 7.0 now that rows are
not limited.
The implementation is fairly straight forward, unfortunately it would break
existing implementations. Other people would have their blobs stored in
LargeObjects ???
Dave
----- Original Message -----
From: "Gunnar Rønning" <gunnar@polygnosis.com>
To: <pgsql-general@postgresql.org>
Cc: <pgsql-jdbc@postgresql.org>
Sent: Friday, June 15, 2001 11:23 AM
Subject: [JDBC] The bytea datatype and JDBC
> I saw Tom Lane mentioning the bytea datatype as the way to do BLOBs for
> tables, but I cannot find anything on it in the documentation and
> it is not supported by the JDBC driver as far as I can see.
>
> Where can I get information about it, so I can go on with implementing
support
> for it ?
>
> Is there any performance differences between using BLOB/OID and bytea ?
>
> I cannot use the OID approach with the application in question as it is
> an JDBC app(Turbine from jakarta.apache.org) that relies on asking the
JDBC
> driver for the datatype. Doing this for an OID column does ofcourse return
> integer while you in some instances would like it to return varbinary.
>
> The Turbine people recommend this patch :
> http://jakarta.apache.org/turbine/howto/postgres-howto.html
>
> I don't like this approach as it may break other usages of OID, so hence
my
> desire to use bytea to get something that works.
>
> Turbine is a quite large and nice web app framework in Java, and it would
be
> nice to see more Turbine users go from mysql to pgsql. But this issue is
> a showstopper for a lot of the people trying...
>
> regards,
>
> Gunnar
>
> --
> Gunnar Rønning - gunnar@polygnosis.com
> Senior Consultant, Polygnosis AS, http://www.polygnosis.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
>
