I'm replying to my own message because I found out the solution to the next
(and final) postgres problem. The problem stems from the fact that the
ResultSetMetaData (used by village) from pgsql identifies the OID field as
an int (which it is in the table, but it really refers to VARBINARY data) so
here's a patch to the pgsql JDBC driver (cvs version):
Index: src/interfaces/jdbc/org/postgresql/Field.java
===================================================================
RCS file:
/home/projects/pgsql/cvsroot/pgsql/src/interfaces/jdbc/org/postgresql/Field.
java,v
retrieving revision 1.1
diff -r1.1 Field.java
118c118
< "int4","oid",
---
> "int4",
129c129,130
< "abstime","timestamp"
---
> "abstime","timestamp",
> "oid"
141c142
< Types.INTEGER,Types.INTEGER,
---
> Types.INTEGER,
152c153,154
< Types.TIMESTAMP,Types.TIMESTAMP
---
> Types.TIMESTAMP,Types.TIMESTAMP,
> Types.VARBINARY
-----Original Message-----
From: Nissim Karpenstein [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 16, 2000 9:20 AM
To: 'Turbine'
Subject: OID [was RE: postgres woes] Patch included
I think for a start, you should change the datatype of the objectdata column
in the visitor table to type oid. That's what you do in Postgres for a
large object column. After you make that change, there's still an exception
on logout: village.DataSetException: Bad conversion:
java.lang.NumberFormatException: <some wierd non-printable chars> I think it
has something to do with the way village processes the large object, and how
pgsql wants you to handle it. I'm looking into it.
<READ THIS>
Also, the word oid is reserved in postgres, so can we please change the name
of the id column in the JobEntry table. I think this requires changes to a
bunch of java files in addition to the schema, and I don't want to break it
so there's no diff for that.
</READ THIS>
Here's the patch for the pgsql schema:
Index: Postgres_users_roles_permissions.sql
===================================================================
RCS file:
/products/cvs/turbine/turbine/docs/schemas/Postgres_users_roles_permissions.
sql,v
retrieving revision 1.1
diff -r1.1 Postgres_users_roles_permissions.sql
83c83
< OBJECTDATA varchar (255), --
oder doch bytea???
---
> OBJECTDATA oid,
-----Original Message-----
From: John Thorhauer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 15, 2000 11:03 PM
To: Turbine
Subject: Re: postgres woes
Julian Coombes wrote:
>
>
> Basically what appears to happen is that the value of OBJECTDATA is
somehow
> being corrupted. The driver gets a call to
>
I was thinking along those lines as I was trying to step through the
code. It looked like it doesnt like the objectdata. Thanks for the
input. Its nice to know that I am not the only one having the problem
;-)
John
--
********************************
** John Thorhauer
** Web Developer
** Phoenix Color Corp.
** [EMAIL PROTECTED]
********************************
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
