From: Lew <noone@lwsc.ehost-services.com>
Subject: Re: Hibernate, web application and only one sequence for all
	primary keys
Date: Fri, 18 Sep 2009 22:38:07 -0400
Organization: albasani.net
Lines: 20
Message-ID: <h91g6g$3la$1@news.albasani.net>
References: <25490498.post@talk.nabble.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <25490498.post@talk.nabble.com>
Cancel-Lock: sha1:JMcBMsfdOdRWL++LZYRbMvqjVAY=
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
To: pgsql-sql@postgresql.org

rawi wrote:
> Grails/Hibernate wishes per default one sequence for all tables-PKs and all
> PKs as BigInt.

How is that a Hibernate default?

Hibernate lets you define a multitude of types as a primary key, and the 
sequence each uses is a matter of XML or annotation configuration, at least in 
the Java version of Hibernate which is the only form of it that I've used. 
I've used both "old-fashioned" Hibernate with *.hbm.xml mapping descriptors, 
and the new-fangled JPA (Java Persistence API) version.

I've used Hibernate with String and (long) integer key types, sequenced and 
not.  For my learning, I use a system on Linux with Java and PostgreSQL.  It 
works just fine.

I'm not familiar with Grails.

-- 
Lew