BaseTZLocation Table (248)
Some tooltip text!
• 1 minute to read
• 1 minute to read
Time zone location for the database (how tz-related datetimes should be stored in the database)
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| BaseTZLocation_id | Primary key | PK | |
| TZLocation_id | Country that this timezone location is defined for | FK TZLocation | |
| validFrom | When is this tzLocation valid from, as THE database timezonelocation | DateTime | |
| databaseId | Actually travelcurrent.current_id, the id of the database this basetimezonelocation is meant for | Id | |
| description | Descriptive text | String(254) | |
| registered | Registered when | UtcDateTime | |
| registered_associate_id | Registered by whom | FK associate | |
| updated | Last updated when | UtcDateTime | |
| updated_associate_id | Last updated by whom | FK associate | |
| updatedCount | Number of updates made to this record | UShort |
Indexes
| Fields | Types | Description |
|---|---|---|
| BaseTZLocation_id | PK | Clustered, Unique |
Relationships
| Table | Description |
|---|---|
| associate | Employees, resources and other users - except for External persons |
| TZLocation | Time zone location |
Replication Flags
- Replicate changes DOWN from central to satellites and travellers.
- Replicate changes UP from satellites and travellers back to central.
- Copy to satellite and travel prototypes.
Security Flags
- No access control via user's Role.