db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zied Hamdi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-712) Support for sequences
Date Tue, 31 Jul 2007 16:14:53 GMT

    [ https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516727

Zied Hamdi commented on DERBY-712:

Hi people there,

I'm using derby as a jee/jpa application endpoint (through hibernate), before I encountred
this missing feature Derby seamed to me the perfect product, evolving drastically even in
performance if I beleive what was said in the sun tech days(compared to mySql). I think the
sequence mecanism is one that should be implemented by a serious database like Derby, one
-but not the only- good reason for that is that persistence frameworks are more and more present
in applications, and to have portability between databases (to be able to migrate to Derby),
it's important to have this feature that I imagine doesn't take a lot to implement / compared
to what it brings to users.

I'll try the @TableGenerator approach, hoping it will work.

Zied Hamdi

> Support for sequences
> ---------------------
>                 Key: DERBY-712
>                 URL: https://issues.apache.org/jira/browse/DERBY-712
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>         Environment: feature request 
>            Reporter: Tony Dahbura
> Would like to see support added for sequences.  This would permit a select against the
sequence to always obtain a ever increasing/decreasing value.  The identity column works fine
but there are times for applications where the application needs to obtain the sequence number
and use it prior to the database write.  Subsequent calls to the table/column would result
in a new number on each call.
> SQL such as the following:
> SELECT NEXT VALUE FOR sequence_name FROM sometable ; would result in a next value.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message