OK, I'll take the responsibility for the increment value for
generators/sequences. It seemed like a good idea at the time. But is it
actually useful for anything?
Based on 25 years of experience, I have to say that the ability to set back
a generator is a terrible idea that has led to more unmaintainable abuse
than other single idea I've had with the possible exception of active
system tables.
In my other systems, sequences can be moved up (necessary for restore) but
never down, never with a settable increment, and never with an explicit
runtime inncrement. Netfrastructure did have a mechanism for distributed
databases that shifted a local sequence with node number in the low bits,
but in general this wasn't good enough to repeat.
AmorphousDB takes sequences (called marks) one step further and gives them
a distinctive datatype so marks don't show up for a general retrieval on a
number. Lacking any concept of primary and foreign keys (or tables for
that matter), marks are the backbone of record relationships.
On Wednesday, April 9, 2014, Simonov Denis <[email protected]> wrote:
> Ability to specify the step for generators / sequences is very good. But I
> think the syntax would be much closer to the standard. So in Oracle / MS
> SQL / Postgresql step instructions for using the keyword INCREMENT BY
> instead STEP
>
> CREATE SEQUENCE name [INCREMENT [BY] increment]
> [MINVALUE minvalue | NO MINVALUE] [MAXVALUE maxvalue | NO MAXVALUE]
> [START [WITH] start] [CACHE cache] [[NO] CYCLE]
>
> moreover it is necessary to describe in
> README.sequence_generators
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
