Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql)

Поиск
Список
Период
Сортировка
От Samuel Gendler
Тема Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql)
Дата
Msg-id AANLkTi=wYc=JOcXUY4ZmrLjYJfsv9d-iy82bUt9hsTiW@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql)  (stagirus <mamasa@stagirus.com>)
Ответы Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql)
Re: [BUGS] Mapping Hibernate boolean to smallint(Postgresql)
Список pgsql-jdbc
subclassing the dialect is almost certainly overkill for what you are trying to accomplish.  Why not just define a UserType that works with a smallint column and then use it in your mappings wherever you need to map a boolean to a smallint.  That will work in Oracle just as it will in postgres, so you won't have an incompatibility that requires a code change in order to switch platforms - it will just be explicit in both platforms.  That's way less invasive (and probably a lot less side effect prone) than trying to modify the dialect.

As for why no one mentioned it, I think that is because probably every one of us thinks that's the worst solution to your problem of all those that have been presented so far. If you lack the experience with hibernate such that you aren't even aware of the existence of the dialect classes, then you probably shouldn't be mucking about with modifying them - especially when hibernate provides a mechanism to solve exactly your problem in the form of user defined types.  I cannot fathom what your resistance to using a user type might be.  Your problem is exactly what they are designed for - to map an arbitrary java class to an arbitrary database structure.  In your case, the user type will be incredibly simple, since it is mapping a built-in type to a single column via a nearly trivial conversion mechanism.  You could fix this in 20 minutes or less with a hibernate book and a user type.



On Fri, Oct 1, 2010 at 9:50 PM, stagirus <mamasa@stagirus.com> wrote:

Of course my very first post on this topic indicated that we were looking for
a solution for a problem with booleans. It took this long for all of us to
reach a conclusion that the business of type mappings are handled by
Hibernate. The following dialect class/API clearly states it.
http://ajava.org/online/hibernate3api/org/hibernate/dialect/PostgreSQLDialect.html#toBooleanValueString(boolean)

Oliver did refer to Hibernate Dialect. Not very clear though. So it is
becoming evident that the types can be managed within Hibernate API or
configurations. Overriding just the above API might suffice. I wish you guys
have pointed me to this earlier.

I am good. thanks.




--
View this message in context: http://postgresql.1045698.n5.nabble.com/Re-BUGS-Mapping-Hibernate-boolean-to-smallint-Postgresql-tp2855367p3073605.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.

--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Oliver Jowett
Дата:
Сообщение: Re: Upgrade to 9 questions
Следующее
От: Samuel Gendler
Дата:
Сообщение: Re: Upgrade to 9 questions