[
https://issues.apache.org/jira/browse/OPENJPA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588238#action_12588238
]
Vincent ASTRUC commented on OPENJPA-569:
----------------------------------------
I have this error with version 1.0.2 and Postgre 8.2 :
org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: column
"administrateddata" is of type bytea but expression is of type oid {prepstmnt
25070683 INSERT INTO USERS (OID, ADMINISTRATEDDATA, CLASSIFICATION, LOGIN,
MODIFICATIONDATETIME, PASSWORD, PREFERENCES, PREFERENCESDATETIME, ROLE,
JDOCLASS, JDOVERSION) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [params=(long)
1002865354472414137, (null) null, (null) null, (String) test, (null) null,
(null) null, (null) null, (null) null, (String) Default, (String)
com.thalesgroup.isr.common.mdd.TypeUsersImpl, (int) 1]} [code=0, state=42804]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:191)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$800(LoggingConnectionDecorator.java:56)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:857)
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1363)
> CLONE -Postgres: bytea vs. oid handling in PreparedStatement.setNull() calls
> ----------------------------------------------------------------------------
>
> Key: OPENJPA-569
> URL: https://issues.apache.org/jira/browse/OPENJPA-569
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.0.2
> Environment: Postgres 8.1 driver, Postgres 8.2 database
> Reporter: Vincent ASTRUC
>
> I'm seeing the following error when running against Postgres. This is solved
> by intercepting the DBDictionary.setNull() call and replacing Types.BLOB with
> Types.BINARY.
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ERROR: column
> "image" is of type bytea but expression is of type oid {prepstmnt 33517025
> INSERT INTO LAZ_Product (id, image, name, price) VALUES (?, ?, ?, ?)
> [params=(long) 1186442009345, (null) null, (String) Browser Spiffer-Upper,
> (float) 31.5]} [code=0, state=42804]
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$800(LoggingConnectionDecorator.java:57)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:858)
> at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
> at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1363)
> at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:95)
> ... 39 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
