openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wes Wannemacher <w...@wantii.com>
Subject Re: id and @GeneratedValue
Date Sun, 17 May 2009 17:30:32 GMT
That is generally a bad idea. Select max(row) will generally initiate
a full index scan or, even worse, a full table scan.

-Wes

On 5/17/09, is_maximum <mnrz57@gmail.com> wrote:
>
> Hello
>
> Can we tell the OpenJPA to automaticall select maximum id from the table to
> set the next id rather than using the OPENJPA_SEQUENCE_TABLE or any other
> database object?
>
> thanks
> --
> View this message in context:
> http://n2.nabble.com/id-and-%40GeneratedValue-tp2916124p2916124.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>


-- 
Wes Wannemacher
Author - Struts 2 In Practice
Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
http://www.manning.com/wannemacher

Mime
View raw message