Expand description
Structured name types for SQL objects.
Structs§
- A fully-qualified human readable name of an item in the catalog.
- A fully-qualified human readable name of a schema in the catalog.
- Whether to resolve an name in the types namespace, the functions namespace, or the relations namespace. It is possible to resolve name in multiple namespaces, in which case types are preferred to functions are preferred to relations.
- An optionally-qualified human-readable name of an item in the catalog.
- An optionally-qualified name of an schema in the catalog.
- A fully-qualified non-human readable name of an item in the catalog using IDs for the database and schema.
- The fully-qualified non-human readable name of a schema in the catalog.
- A set of IDs resolved by name resolution.
Enums§
- Comments can be applied to multiple kinds of objects (e.g. Tables and Role), so we need a way to represent these different types and their IDs (e.g.
GlobalIdandRoleId), as well as the inner kind of object that is represented, e.g.GlobalIdis used to identify both Tables and Views. No other kind of ID encapsulates all of this, hence this new “*Id” type. - The identifier for a database.
- A human readable name of a database.
- An id of a database.
- The identifier for a schema.
- An id of a schema.
Constants§
Statics§
Functions§
- Resolves names in an AST node using the provided catalog.