varbinary columns in postgresql

[Nick Pomfret <ni...@pixelpark.com>]

I've posted this before but didn't manage to get it cleared up.

After installing the sample app that comes with TDK, and modifying the
postgresql driver to work with oid fields, i get the following error in
turbine.log after adding a new user:

[Mon Oct 08 09:37:52 BST 2001] -- ERROR -- Error rendering Velocity
template: sc
reens/user/FluxUserList.vm: Error rendering Velocity template:
screens/user/Flux
UserList.vm: Invocation of method 'getUsers' in  class
org.apache.turbine.flux.t
ools.FluxTool threw exception class
org.apache.turbine.util.security.DataBackend
Exception

A row was entered in the database and the other forms (such as the groups
form) appear to be working correctly.


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org

Re: varbinary columns in postgresql

[Santiago Gala <sg...@hisitech.com>]

Nick Pomfret wrote:

>I've posted this before but didn't manage to get it cleared up.
>
>After installing the sample app that comes with TDK, and modifying the
>postgresql driver to work with oid fields, i get the following error in
>turbine.log after adding a new user:
>
>[Mon Oct 08 09:37:52 BST 2001] -- ERROR -- Error rendering Velocity
>template: sc
>reens/user/FluxUserList.vm: Error rendering Velocity template:
>screens/user/Flux
>UserList.vm: Invocation of method 'getUsers' in  class
>org.apache.turbine.flux.t
>ools.FluxTool threw exception class
>org.apache.turbine.util.security.DataBackend
>Exception
>
>A row was entered in the database and the other forms (such as the groups
>form) appear to be working correctly.
>
I think the problem is that village writes varbinary objects using 
connection.setBytes(), and this will not work with portgres cvs drivers 
for oid fields (patched or not), at least until 7.2 is out and we get 
better bytea support. If village used connection.setObject() it *could* 
work with patches applied to the jdbc driver.

In Jetspeed we are using a text DB field (instead of oid) for postgres 
varbinary objects, as this data type can handle byte arrays, which the 
postgres jdbc driver sends always as quoted strings to the backend.

The JDBC driver in postgres is a real mess, as it is changing very fast. 
I think the patch as marked in turbine web page is not valid anymore. So 
take my comments with a grain of salt :-)

>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>




---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org