[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4876) Postgresql @Lob problem

Julien Serdaru (JIRA) noreply at atlassian.com
Thu Oct 14 17:28:47 EDT 2010


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38745#action_38745 ] 

Julien Serdaru commented on HHH-4876:
-------------------------------------

Are there any plans to fix this in 3.5?
This issue prevents us from migrating to 3.5. We use an external library that ships @Lob-annotated entity classes which breaks on PostgreSQL.

Thanks!

> Postgresql @Lob problem
> -----------------------
>
>                 Key: HHH-4876
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4876
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: annotations
>    Affects Versions: 3.5.0-Beta-4
>         Environment: Reproducable on Windows and Linux with Postgresql 8.4
>            Reporter: Radosław Smogura
>            Assignee: Strong Liu
>
> The current version of Hibernate (Beta) wrongly reads PgSQL blob values (mapped from @Lob byte[]). In general Hibernate properly creates OID type columns for storing blobs, but when it read blob it reads oid value instead of LOB referenced by oid valu (so as the output i get 6 bytes length table instead of 120kb table) This works fine in previous release 3.3 / 3.2.
> This was I saw is: previous version uses getBlob(), but 3.5 version uses getBytes() of resultset class.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the hibernate-issues mailing list