|Purpose||Data types used by the DBMS_CRYPTO packages
According to the source file header:
--- Old dbms_crypto_TOOLKIT code.
--- The code below was desupported and should not be documented.
--- Final disposition on the removal of this package is pending.
--- December 12, 2002
Apparently someone forgot about this sometime during the preceding 16 years. The script was last altered, according to the header, in 2014 ... 12 years after it was "desupported".
/* This data structure describes an identity. An identity may either be myself (a persona) or another trusted identity */
/* This record contains the printable alias for a persona as well as the complete identity and persona. NOTE: the size of the persona field must match that contained within the Persona type. PL/SQL will not allow a record to contain another record so the Persona could not be used directly. */
/* This data structure is a place holder until it is determined what private information is needed to create a persona. */
|Security Model||Owned by SYS with no privileges granted|
|Crypto Opaque Data Types|
|Opaque Datatypes||-- These data types are intended to be opaque. The contents of the
-- records are either not visible to the caller or are to be accessed
-- using convenience functions. Unfortunately, PL/SQL does not allow
-- type definitions to be hidden inside the package bodies.
-- Records are used in order to enforce type checking as PL/SQL will
-- otherwise do automatic type conversion.
-- Dummy variables are used to get around PL/SQL restriction which does
-- not allow constrained subtypes, e.g. SUBTYPE foo is VARCHAR(15) is
-- not allowed.
|What's New In 18cR3|
|What's New In 19cR3|
|This site is maintained by Dan Morgan. Last Updated:||This site is protected by copyright and trademark laws under U.S. and International law. © 1998-2019 Daniel A. Morgan All Rights Reserved|