Try OpenEdge Now
skip to main content
Configuring Multi-tenancy
Working with sequences : Working with sequences and sequence values : Sequence functionality and user credentials
 

Sequence functionality and user credentials

Access to sequences and their values depends on the credentials of the user who has established the database connection. To be able to access and edit the current values, the user whose credentials were supplied at login must be either a super-tenant or a user of the tenant whose sequence values are being accessed. If the user is a super-tenant user, the user can access sequence current values for all tenants.
As a user of the regular tenant whose sequence values you want to work with, you can:
*View a list of sequences with details that include, for example, whether a sequence is enabled for multi-tenancy; a sequence's initial value; and a sequence's increment value.
*Edit the current values for shared sequences.
*Edit a tenant's current values for the shared sequences.
*Edit a tenant's current values for the multi-tenant sequences (provided that the user whose credentials were provided at database connection is a user of that tenant).
*Preview sequence definitions when loading a data definition file.
*Export to a file the current values for all multi-tenant.
*Export to a file the current values for shared sequences for the tenant (provided that the user whose credentials were provided at database connection is a user of that tenant).
Database connection user credentials for a super-tenant user permit the user to do all of the above as well as the following tasks:
*Edit the current values for all tenants of a multi-tenant sequence.
*Export by tenant the current values for all regular tenants to individual files. Each tenant has an individual file that contains the current sequence values for all multi-tenant sequences. For each tenant, an export file is created and holds the current sequence values for that tenant for each multi-tenant sequence.
The super-tenant does not have its own sequence data; therefore, when you export sequence values for multi-tenant sequences, no file is generated.
When a tenant is added to the database, a current sequence value (set to the initial value) is stored for the tenant for each multi-tenant sequence. When a tenant is removed from a database, each multi-tenant sequence and its current value for that tenant is dropped from the database.
You cannot currently convert a shared sequence to a multi-tenant sequence. However, you can add multi-tenant sequences, created in the Data Dictionary tool, to a database by loading a data definition file (.df) that contains them.