dbo.custom_fields (Custom fields)
Documentation | Dataedo repository 7 |
Schema | dbo |
Name | custom_fields |
Title | Custom fields |
Module | Custom fields |
Type | Metadata |
Status | Active |
Table holds definition of custom fields - metadata fields defined by Dataedo admin.
Availability
Availability for field is stored in following bit columns:
- table_visibility
- procedure_visibility
- column_visibility
- relation_visibility
- key_visibility
- trigger_visibility
- parameter_visibility
- module_visibility
- documentation_visibility
Field table column
Custom fields values are saved in the same tables as objects they are assigned to, e.g. fields in for Parameters are saved in dbo.parameters table in columns field1 to field40.
Below example shows how to find physical values in Dataedo repository tables.
Imagine Sensitive Data custom field:
You can find where this value is stored in column field_name in field form or in custom_fields table. In this case it is field6.
So to find Sensitive Data values in columns you need to look into field6 column in columns table.
Columns
Key | Name | Data type | Null | Attributes | References | Description | Type | Status | ||
---|---|---|---|---|---|---|---|---|---|---|
1 | custom_field_id | int | Identity | Row id | Metadata | Active | ||||
Row id Identity Type: Metadata Status: Active |
||||||||||
2 | title | nvarchar(250) | Field displayed name | Documentation | Active | |||||
Field displayed name Type: Documentation Status: Active |
||||||||||
3 | type | nvarchar(100) | Default: N'TEXT' | Field type:
TEXT - plain text field, LIST_CLOSED - closed drop-down LIST_OPEN - open drop-down MULTI_VALUE_LIST_CLOSED - closed multi-select drop-down INTEGER - number CHECKBOX - checkbox |
Metadata | Active | ||||
Field type:
TEXT - plain text field, LIST_CLOSED - closed drop-down LIST_OPEN - open drop-down MULTI_VALUE_LIST_CLOSED - closed multi-select drop-down INTEGER - number CHECKBOX - checkbox Default: N'TEXT' Type: Metadata Status: Active |
||||||||||
4 | code | nvarchar(255) | Text code set on creation of the field | Metadata | Active | |||||
Text code set on creation of the field Type: Metadata Status: Active |
||||||||||
5 | field_name | nvarchar(50) | Name of the column in physical tables where custom field is stored, e.g. field1 (which is in all schema tables, i.e. tables.field1, columns.field1...) | Metadata | Active | |||||
Name of the column in physical tables where custom field is stored, e.g. field1 (which is in all schema tables, i.e. tables.field1, columns.field1...) Type: Metadata Status: Active |
||||||||||
6 | definition | nvarchar(MAX) | List of values for lists as text separated with commas. E.g. 'Blue, Red, Green' | Metadata | Active | |||||
List of values for lists as text separated with commas. E.g. 'Blue, Red, Green' Type: Metadata Status: Active |
||||||||||
7 | ordinal_position | int | User sorting column | Metadata | Active | |||||
User sorting column Type: Metadata Status: Active |
||||||||||
8 | description | nvarchar(MAX) | Custom field admin comments | Metadata | Active | |||||
Custom field admin comments Type: Metadata Status: Active |
||||||||||
9 | table_visibility | bit | Default: 1 | Is field available for tables and views (columns are defined separately) | Metadata | Active | ||||
Is field available for tables and views (columns are defined separately) Default: 1 Type: Metadata Status: Active |
||||||||||
10 | procedure_visibility | bit | Default: 1 | Is field available for procedures and functions (columns are defined separately) | Metadata | Active | ||||
Is field available for procedures and functions (columns are defined separately) Default: 1 Type: Metadata Status: Active |
||||||||||
11 | column_visibility | bit | Default: 1 | Is field available for tables' and views' columns | Metadata | Active | ||||
Is field available for tables' and views' columns Default: 1 Type: Metadata Status: Active |
||||||||||
12 | relation_visibility | bit | Default: 1 | Is field available for table/view relations | Metadata | Active | ||||
Is field available for table/view relations Default: 1 Type: Metadata Status: Active |
||||||||||
13 | key_visibility | bit | Default: 1 | Is field available for table/view primary/unique keys | Metadata | Active | ||||
Is field available for table/view primary/unique keys Default: 1 Type: Metadata Status: Active |
||||||||||
14 | trigger_visibility | bit | Default: 1 | Is field available for triggers | Metadata | Active | ||||
Is field available for triggers Default: 1 Type: Metadata Status: Active |
||||||||||
15 | parameter_visibility | bit | Default: 1 | Is table available for parameters | Metadata | Active | ||||
Is table available for parameters Default: 1 Type: Metadata Status: Active |
||||||||||
16 | module_visibility | bit | Default: 1 | Is field available for modules | Metadata | Active | ||||
Is field available for modules Default: 1 Type: Metadata Status: Active |
||||||||||
17 | documentation_visibility | bit | Default: 1 | Is field available for documentation | Metadata | Active | ||||
Is field available for documentation Default: 1 Type: Metadata Status: Active |
||||||||||
18 | creation_date | datetime | Default: getdate() | Standard row creation timestamp | Metadata | Active | ||||
Standard row creation timestamp Default: getdate() Type: Metadata Status: Active |
||||||||||
19 | created_by | nvarchar(1024) | Default: suser_sname() | Dataedo username that created row | Metadata | Active | ||||
Dataedo username that created row Default: suser_sname() Type: Metadata Status: Active |
||||||||||
20 | last_modification_date | datetime | Default: getdate() | Standard row last update timestamp | Metadata | Active | ||||
Standard row last update timestamp Default: getdate() Type: Metadata Status: Active |
||||||||||
21 | modified_by | nvarchar(1024) | Default: suser_sname() | Dataedo username that last updated row | Metadata | Active | ||||
Dataedo username that last updated row Default: suser_sname() Type: Metadata Status: Active |
||||||||||
22 | source_id | int | For internal use only | Internal | Active | |||||
For internal use only Type: Internal Status: Active |
Relations
Foreign table | Primary table | Join | Title / Name / Description | |
---|---|---|---|---|
dbo.custom_fields_values (Custom fields Index) | dbo.custom_fields (Custom fields) | dbo.custom_fields_values.custom_field_id = dbo.custom_fields.custom_field_id | FK_custom_fields_values_custom_fields | |
dbo.custom_fields_values.custom_field_id = dbo.custom_fields.custom_field_id Name: FK_custom_fields_values_custom_fields |
||||
dbo.documentation_custom_fields | dbo.custom_fields (Custom fields) | dbo.documentation_custom_fields.custom_field_id = dbo.custom_fields.custom_field_id | FK_documentation_custom_fields_custom_fields | |
dbo.documentation_custom_fields.custom_field_id = dbo.custom_fields.custom_field_id Name: FK_documentation_custom_fields_custom_fields |
Unique keys
Key name | Columns | Description | |
---|---|---|---|
PK_custom_fields | custom_field_id | Table primary key | |
Table primary key | |||
UK_custom_fields_code | code | Code must be unique | |
Code must be unique | |||
UK_custom_fields_field_name | field_name | Any physical column in Dataedo repository that holds custom fields must obviously be used just by one field | |
Any physical column in Dataedo repository that holds custom fields must obviously be used just by one field | |||
UK_custom_fields_title | title | Field name must be unique | |
Field name must be unique |
Triggers
Key name | When | Description | |
---|---|---|---|
trg_custom_fields_Modify | After Insert, Update |
Uses
Name |
---|
dbo.trg_custom_fields_Modify
|
dbo.custom_fields (Custom fields)
|
Used by
Name |
---|
dbo.custom_fields (Custom fields)
|
dbo.trg_custom_fields_Modify
|
Exported: 2018-12-06 15:15, Last imported: 2018-11-21 15:07