[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2244) Problem with data type 'Blob'

[Xavier Bugaud (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2244?page=comments#action_25323 ] 

Xavier Bugaud commented on HHH-2244:
------------------------------------

If JDBC consider that a blob must be part of a row, then you're right : this problem must be solved outside Hibernate (with a trigger or by running vacuumlo periodicaly).
If not, Hibernate has to remove the blob when needed.

Can you please tell me where in the JDBC specs is written that a blob must be part of the row ? I can't find something clear about that in the JDBC API or in the Sun JDBC documentation.

Regards,

> Problem with data type 'Blob'
> -----------------------------
>
>          Key: HHH-2244
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2244
>      Project: Hibernate3
>         Type: Bug

>  Environment: Hibernate version:3.2
> DB: postgresql 8.1
>     Reporter: Gulshanrai BABAJEE

>
>
> I have created a table in which I have a field of type BLOB which I store pictures. I insert a picture, note the oid generated. Then I do the following select statement on table 'pg_largeobject' (system table) : select * from pg_largeobject where loid = 'oid of my picture'. I found the oid.
> Then I update my picture. Its oid has been changed. I now make another select from table 'pg_largeobject' where loid = 'my OLD oid' and I was surprised to see that the old oid is STILL in the table. So I conclude that each time I update a picture from my table. The old oids are still there and eventually my database is increasing in size.
> Is this not a bug in hibernate?
> thanks in advance 

-- 
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