On Wed, 2002-07-31 at 12:16, André van Toly wrote:
> We're been using PostgreSQL 7.2.1. For some reasons (i believe the
> new one is faster) we replaced the current jdbc driver
> (jdbc7.1-1.2.jar) with a new one (jdbc7.2dev-1.2.jar) and ran into
> troubles uploading images. It seems that in 7.2 PostgreSQL stores
> images in a different datatype (i learned this via Ricardo of IC&S
> who find it in www.dejanews.com searching for 'jdbc postgresql image
> 7.2' :-)
I cant find it:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=jdbc+postgresql+image+7.2
<old email>
.....
the jxDbCon driver for PostgreSQL and run some jMeter
tests against it.
With 100 simultaneous threads the native library shows a performance
gain of roughly 20%.
(Per thread a connection pool of 1 connection was used)
[skipped the diagrams]
</old email>
> 1.
> Should the configuration file for PostgreSQL in MMBase in
> config/databases/postgresql71.xml be changed?
> Maybe into config/databases/postgresql72.xml?
Guess that the jdbc driver converts the OID into a bytea then. Since
this behaviour is caused by the JDBC driver(are you sure you use as
classe the Postgresql71? and postgresql71.xml as the config file?)
>
> 2.
> And what exactly should i change?
> <type-mapping mmbase-type="BYTE">OID</type-mapping> into
> <type-mapping mmbase-type="BYTE">bytea</type-mapping> ?
Well, since OID is specified, it should create type OID for this field.
Changing it to bytea could only help you if your data inside the
database is of type bytea
To clearify:
You created the table image using the old jdbc driver and it was an
'OID' field,
Now you try to read/add/delete data on the image table with the new
jdbc driver since it expects the type 'bytea' ?
--
Eduard Witteveen Systeem Ontwikkelaar
NOS Internet, Gateway C Kamer 107
+31(0)356772910 http://www.omroep.nl/
Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
