The table will be named type(x) and the foreign key will always be enum. tk(x): This is a type key (enumerator) in another table.The table will be named (x) and the "_(y)" is a descriptor which usually indicates that in a given record there is more than one field pointing to the same foreign table. fk(x)_(y): This is a foreign key (unique value) in another table.That table will be named (x) and the foreign key field will always be pkid. fk(x): This is a foreign key (unique value) in another table.Whenever a field in a table is linked to another table or another record in the same table, the following field name conventions are used: Enumeration or "type" tables also have a unique key that is always named: enum. Standard tables and mapping tables use a unique key that is always named: pkid. Mapping Tables: Basically connects unique records from one table to unique records in another table. That is understating their purpose somewhat, but from a SQL query point of view you will use type tables mainly to resolve enumerator values to a human readable format.
Standard Tables: Tables which contain the core data values of a particular object like devices, number patterns, end users, etc.Įnumeration or "type" Tables: Used by other tables to resolve enumerator IDs to some name or moniker. I classify tables in the CUCM databases into three (3) categories: Anyone looking to build a custom query to run against their CUCM system may want to take a look at the following resources:
0 kommentar(er)
