Session Constraint Values for Directory Users - Teradata Database
SQL Data Definition Language Syntax and Examples
- Deployment
- VantageCloud
- VantageCore
- Edition
- VMware
- Enterprise
- IntelliFlex
- Product
- Teradata Database
- Release Number
- 20.00
- Published
- June 2025
- ft:locale
- en-US
- ft:lastEdition
- 2026-09-23
- dita:mapPath
- mbm1747160743883.ditamap
- dita:ditavalPath
- jlp1749501702948.ditaval
- dita:id
- mdr1472255012272
- lifecycle
- latest
- A directory user who is mapped to a permanent user inherits the permanent user privileges and constraint assignments.
- A directory user who is not mapped to a permanent database user, but who uses Sign-On As to log on as a permanent user, inherits the user privileges and constraint assignments.
- Directory users who are mapped to multiple constraint value sources (users or profiles) must use the user=user_name or profile=profile_name option in the logon string to specify the source for default constraint values and OVERRIDE privileges.
- Directory users can use the SET SESSION CONSTRAINT option to access any mapped or inherited constraint assignments.
- For directory users with no mappings and only PUBLIC or EXTUSER privileges, the session constraint value is NULL, and the user cannot access row level security tables.