Skip site navigation (1) Skip section navigation (2)

The bytea datatype and JDBC

From: Gunnar Rønning <gunnar(at)polygnosis(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: The bytea datatype and JDBC
Date: 2001-06-15 16:02:46
Message-ID: m2bsnp91eh.fsf@smaug.polygnosis.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-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(at)polygnosis(dot)com
Senior Consultant, Polygnosis AS, http://www.polygnosis.com/

Responses

pgsql-jdbc by date

Next:From: Dave CramerDate: 2001-06-15 17:53:33
Subject: Re: [JDBC] The bytea datatype and JDBC
Previous:From: Gunnar RønningDate: 2001-06-15 15:23:10
Subject: The bytea datatype and JDBC

pgsql-general by date

Next:From: Martín MarquésDate: 2001-06-15 16:09:16
Subject: Re: Re: Log files, how to rotate properly
Previous:From: Thalis A. KalfigopoulosDate: 2001-06-15 15:59:40
Subject: Re: CLUSTER. (fwd)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group