Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues
| От | Oliver Jowett |
|---|---|
| Тема | Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues |
| Дата | |
| Msg-id | CA+0W9LMpZOScfZaQU8r+bkrS7Bm-iu=3=FBsOi-5DL4Q6jFfQw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] Binary Large Objects (LOB/BLOB) in Hibernate and JDBC: Unresolved issues (Oliver Jowett <oliver@opencloud.com>) |
| Список | pgsql-jdbc |
On 10 January 2012 00:29, Oliver Jowett <oliver@opencloud.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
В списке pgsql-jdbc по дате отправления: