Ok, time for me to jump out of the shadows :-).
I'm in exactly the same position regarding Turbine/Postgresql jbdc7.0-1.2.jar
from the Postgresql CVS as of yesterday.
I've been debugging the jdbc driver and have the following trace, which is the
result of pressing the logout button.
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- PreparedStatement - sql: UPDATE
Visitor SET loginid = ?, password_value = ?, first_name = ?, last_name = ?, lasttlogin
= ?, objectdata = ? WHERE VISITORID = ?
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [0] string: UPDATE Visitor
SET loginid =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [1] string: ,
password_value =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [2] string: , first_name =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [3] string: , last_name =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [4] string: , lastlogin =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [5] string: , objectdata =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [6] string: WHERE
VISITORID =
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- template [7] string:
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 1 to
'turbine'
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 2 to
'turbine'
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 3 to
'turbine'
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 4 to
'turbine'
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 5 to
'2000-06-16 00:49:31.0'
[Fri Jun 16 00:55:32 GMT+00:00 2000] -- NOTICE -- ----Driver: Setting param 6 to
'¬ísrjava.util.Hashtable»%!Jä¸F
Basically what appears to happen is that the value of OBJECTDATA is somehow
being corrupted. The driver gets a call to
PreparedStatement.setString(int ParameterIdx ,String x)
and checks the value passed != null. If the value does equal null then the
string "null" is put in the prepared statement.
When the OBJECTDATA comes across to the to the PreparedStatement its full of
junk and blows up the jdbc driver.
I hacked the jdbc driver to stick a "null" in the call on the sixth parameter,
and everything appeared to work fine. Obviously this isn't a long term solution
:-).
Anyway, there you have it, I'm sure there's someone out there who can check the
integrity of OBJECTDATA. My suspicion is that the cause has something to do
with OBJECTDATA's dual life as a byte array and a String.
Julian.
On Fri, 16 Jun 2000, you wrote:
> OK... I am slowly getting turbine to work with postgres but now I am
> getting another error when I click the logout button. Here is the
> error:
>
> ######################################33
> Exception: java.sql.SQLException: ERROR: Unterminated quoted string
>
> at org.postgresql.Connection.ExecSQL(Connection.java:393)
> at org.postgresql.jdbc2.Statement.execute(Statement.java:273)
> at
> org.postgresql.jdbc2.Statement.executeUpdate(Statement.java:73)
> at
> org.postgresql.jdbc2.PreparedStatement.executeUpdate(PreparedStatement.java:126)
> at
> com.workingdogs.village.Record.saveWithUpdate(Record.java:284)
> at com.workingdogs.village.Record.save(Record.java:187)
> at com.workingdogs.village.Record.save(Record.java:166)
> at
> org.apache.turbine.om.peer.BasePeer.insertOrUpdateRecord(BasePeer.java:686)
> at
>
--
Julian R. Coombes
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
