[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4876?page=c...
]
Radosław Smogura commented on HHH-4876:
---------------------------------------
Hm... it doesn't sound good, because it's breaks current system. Is there any
chance to revert reading blobs using blob.getBytes(), in a way of some configuration
parameter, or put back the PrimitiveByteArrayBlobType so I could annotate my @Lob wit
@Type("old_working_blob") :)
In any way I want to thank you for above information, as I now know what to change to make
it work (unfortunate I can't build trunk to jar, because of test fails).
And by the way, I've forgotten to mention this
When Hibernate creates @Lob byte[] column it sets it's type to oid - this will cases
full trip "create -> use" to fail (from above reasons).
Postgresql @Lob problem
-----------------------
Key: HHH-4876
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4876
Project: Hibernate Core
Issue Type: Bug
Components: core
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira