From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
Cc: | Radosław Smogura <rsmogura(at)softperience(dot)eu>, pgsql-general List <pgsql-general(at)postgresql(dot)org>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues |
Date: | 2012-01-09 11:41:27 |
Message-ID: | CA+0W9LMpZOScfZaQU8r+bkrS7Bm-iu=3=FBsOi-5DL4Q6jFfQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
On 10 January 2012 00:29, Oliver Jowett <oliver(at)opencloud(dot)com> wrote:
> So I'm still confused about what you'd like to see changed in the JDBC
> driver. Can you explain?
Perhaps what you're looking for here is "it all just works out of the
box". In that case, the missing piece seems to be that the DDL that
Hibernate emits (or the DDL which you have set up by hand - I don't
know how you have things set up) does not match the data model that
Hibernate is expecting. If Hibernate is expecting a data model where
the lifecycle of the LO is managed by the database and there's only at
most one reference to a particular LO (i.e. you can't link to the same
LO from multiple places), then it can set up appropriate cleanup
triggers on LO columns as part of its DDL automatically. Or it could
just map blobs to bytea, which might be a more natural mapping in that
case anyway and doesn't require triggers etc. So you'd need to talk to
the Hibernate guys about making those changes.
Oliver
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2012-01-09 12:26:46 | Re: Supporting SQL/MED DATALINK |
Previous Message | John R Pierce | 2012-01-09 11:36:39 | Re: Supporting SQL/MED DATALINK |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2012-01-09 12:08:52 | Re: problem: query result in jdbc is <> result in psql |
Previous Message | Oliver Jowett | 2012-01-09 11:29:03 | Re: Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues |