#1417 new
Tom Eicher

allow per-model sequence value

Reported by Tom Eicher | February 8th, 2012 @ 07:57 PM

When a Play App is run against a database that uses sequences rather than autoincrement, all model entities share the same ID sequence and thus have the same "numberspace".
(e.g. new Login gets 1, new BlogPost gets 2, new Login gets 3, new Comment gets 4, new BlogPost gets 5... so the 2 entities in "BlogPost" now have IDs 2 and 5, with no 1, 3, 4, ...)

While this is technically ok, and in postgres you can get gaps in the sequence due to rollbacked transactions,
many people would still prefer to have a "numberspace per model entity".

Model has

    public Long id;

and there is no way to put an override like

    @SequenceGenerator(name = "BlogPostSeq", sequenceName = "BlogPostSeq")
    @GeneratedValue(generator = "BlogPostSeq")

of course this limitation stems from JPA, but as you recommend using models.Event,
it would be very good if you found a way to optionally provide the sequence name to
any class extending Model..

Framework version:
play! 1.2.4

Reproduction steps:
run any app with more than 1 model against a postgres database.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket