[reporter="jpham", created="Thu, 18 May 2006 14:06:56 -0500 (GMT-05:00)"]
The auto increment feature allows columns to have their
values automatically generated according to a sequence,
(ex. 0,1,2, ... or 100, 110, 120,...). These columns are also
known as "identity columns".
An existing test case is at:
farrago/unitsql/ddl/sequence.sql
Broadbase has a few at:
bb/server/Test/sequences/...
The LucidDB implementation has several differences from
the broadbase implementation:
(1) Broadbase has sequence objects while LucidDB has identity columns
- LucidDB columns are typed
(2) The options are somewhat different
- Broadbase uses start/end, while LucidDB uses minvalue maxvalue
- Broadbase has cache options which LucidDB does not
(3) The first value returned differs
- Broadbase returns start+increment, while LucidDB returns start
(4) validation rules differ, for example
- LucidDB allows you to restart values
[reporter="jpham", created="Thu, 18 May 2006 14:06:56 -0500 (GMT-05:00)"] The auto increment feature allows columns to have their
values automatically generated according to a sequence,
(ex. 0,1,2, ... or 100, 110, 120,...). These columns are also
known as "identity columns".
Please reference this document for background info:
http://eigenbase.wikispaces.com/AutoincrementColumns
An existing test case is at:
farrago/unitsql/ddl/sequence.sql
Broadbase has a few at:
bb/server/Test/sequences/...
The LucidDB implementation has several differences from
the broadbase implementation:
(1) Broadbase has sequence objects while LucidDB has identity columns
- LucidDB columns are typed
(2) The options are somewhat different
- Broadbase uses start/end, while LucidDB uses minvalue maxvalue
- Broadbase has cache options which LucidDB does not
(3) The first value returned differs
- Broadbase returns start+increment, while LucidDB returns start
(4) validation rules differ, for example
- LucidDB allows you to restart values