Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

> ## gsc_next_sequence table — gscsn

> This table allocates sequence numbers where multiple sequence numbers might be requested by multiple transactions simultaneously. It is intended to avoid “deadly embrace” record locks.

> Table 12–3 lists the table’s FLA, fields, and foreign keys.

> Table 12–3: gsc_next_sequence table information
> Table FLA | Fields (data type) | Foreign keys
> --- | --- | ---
> gscsn | sequence_obj (Decimal) next_sequence_value (Integer) next_sequence_obj (Decimal) | sequence_obj

> Table 12–4 gives details of the table’s indexes.

> Table 12–4: gsc_next_sequence index information
> Index name | Elements | Type
> --- | --- | ---
> XPKgsc_next_sequence | sequence_obj next_sequence_value | Primary Unique

> When a sequence is created or updated on the `gsc_sequence` table with the `multi_transaction` field set to `YES`, a number of sequence records equal to the `number_of_sequences` field’s value are created in this table. The new sequence numbers start with the value listed in the `next_sequence_value` field.

> When a sequence number is requested, the first record in this table for the `gsc_sequence` is found, saved, and deleted. At the same time, a new `gsc_next_sequence` record is tagged on the end, with the sequence number just found plus the `number_of_sequences` value.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095