Re: [HACKERS] JPA + enum == Exception
Dave Cramer <pg@fastcrypt.com>
From: Dave Cramer <pg@fastcrypt.com>
To: Tom Dunstan <pgsql@tomd.cc>
Cc: Andreas Joseph Krogh <andreak@officenet.no>,
"pgsql-jdbc@postgresql.org" <pgsql-jdbc@postgresql.org>
Date: 2013-07-05T09:57:42Z
Lists: pgsql-hackers
I would think setObject should respect stringtype=unspecified. So I would be willing to accept this as a solution Dave Cramer dave.cramer(at)credativ(dot)ca http://www.credativ.ca On Fri, Jul 5, 2013 at 5:47 AM, Tom Dunstan <pgsql@tomd.cc> wrote: > Hi Andreas > > On 5 July 2013 18:51, Andreas Joseph Krogh <andreak@officenet.no> wrote: > >> I've been using Hibernate for years with mapping Enums to varchar-columns >> which works fine. Remember to map them with >> > > I'm not trying to map them to varchar columns - I'm trying to map them to > columns with postgresql enum types as created by CREATE TYPE, see e.g. > http://www.postgresql.org/docs/9.2/static/datatype-enum.html. The > built-in enum types are designed for that purpose, and perform better and > more safely than using varchars. > > Mapping java enums to a typesafe and efficient version in the db was the > main reason I did the work to add native enums to postgresql in the first > place - I haven't had a chance to use it recently, and I'm a bit > disappointed that it doesn't work out of the box. So I want to fix up > whatever parts of the stack are in the way of making that work. > > Cheers > > Tom >