OpenEdge Getting Started: Multi-tenancy Overview - Product ...

Super-tenant data updates
ABL Support
ABL allows a super tenant to create (with can-create access) and update (with
can-write or can-delete access, as appropriate) database records for specified tenants
using the following elements:
• CREATE statement and BUFFER-CREATE( ) method on a buffer handle — For a
multi-tenant table, these ABL elements provide an option for a super tenant to
create a database record for a specified tenant, regardless of the effective
tenancy. Without this option, these ABL elements create database records owned
by the effective tenant.
• All record update statements, such as ASSIGN, SET, UPDATE, DELETE, etc. —
Regardless of the current effective tenant, ABL remembers the tenancy of all
records created for a multi-tenant database as well as the records retrieved from
a multi-tenant database. When a super tenant updates database records created
for multiple tenants or queried for multiple tenants, ABL ensures that all these
record instances are written to or deleted from the table instances owned by the
corresponding tenants.
Tenancy identification
Tenancy is identified by:
• A name that you assign when you configure the tenant in a multi-tenant database.
• A database-unique, integer ID that OpenEdge assigns when you first create the
tenant. The default tenant ID is zero (0), all other regular-tenant IDs are positive
integers, and all super-tenant IDs are negative integers.
A super tenant can return information about database connection tenancy using these
ABL built-in functions:
• IS-DB-MULTI-TENANT function — Returns TRUE if a connected database is
multi-tenant enabled.
• TENANT-NAME and TENANT-ID function — Returns the tenant identity associated
with a current database connection identity.
• TENANT-NAME-TO-ID function — Returns the tenant ID, given the tenant name
associated a current database connection identity.
• GET-EFFECTIVE-TENANT-NAME and GET-EFFECTIVE-TENANT-ID function —
Returns the current effective tenant identity for a connected database.
Note, again, that the GET-EFFECTIVE-TENANT-* functions return the most recent
effective tenancy for a database connection, where as the corresponding TENANT-*
functions return the tenancy of the current database connection identity. The
effective tenancy for a database connection is set only using the
SET-EFFECTIVE-TENANT function, where as the connection identity can be set using
any connection authentication operation. These two tenancies can be different, with the
most recently set tenancy overriding the other for purposes of effective tenancy.
OpenEdge Getting Started: Multi-tenancy Overview 57