Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <42CE501C.10604@optusnet.com.au>
Date: Fri, 08 Jul 2005 20:06:20 +1000
From: Gianny Damour <gianny.damour@optusnet.com.au>
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: PK Generator Status
References: <Pine.LNX.4.58.0507072118310.4265@saturn.opentools.org>
In-Reply-To: <Pine.LNX.4.58.0507072118310.4265@saturn.opentools.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

On 8/07/2005 11:28 AM, Aaron Mulder wrote:

>	So I've put in the new PK generator configuration syntax.  Once 
>again, the openejb-jar.xml syntax has changed.  The old style of declaring 
>a separate PK Generator GBean is still supported, but with a different 
>element.  I'm going to update the wiki shortly.
>
>	There are some TranQL enhancements that would be nice:
>
>1) Implement a PK Generator that handles an EJB on a table that 
>automatically populates a PK value in itself (via an AUTO_INCREMENT column 
>or a trigger or whatever).  I think it would basically just hold a column 
>name, and then the part of TranQL that created entities would need logic 
>to recognize that, perform the insert as usual, and then fetch the PK ID 
>value as an auto-generated key afterward.
>  
>
org.tranql.pkgenerator.AutoIncrementTablePrimaryKeyGenerator does that.

Thanks,
Gianny

>2) If the option is implemented to dump DDL on startup, add the DDL for 
>each PK Generator too (with, for example, the INSERTs necessary for a 
>sequence table generator).  I like that more than having the PK Generator 
>try to initialize its own tables or whatever on every startup and just 
>suppress any exceptions.
>
>Aaron
>
>  
>