Extending Microsoft Dynamics 365 Finance and Supply Chain Management Cookbook - Second Edition
by Simon Buxton
How it works...
Table inheritance is not implemented as physical data structures as we might assume. The natural presumption of how this works is that each child table we create is represented as a physical table in the SQL Server and that there is some logical mechanism that joins them together in the application. In fact, there is only one physical table, and the fields from all the tables are stored in this table. The separation is logical and is a useful way to abstract data into logical entities.
We can see that when we issue a SELECT * FROM <BaseTable> in a SQL Server query window, we get all the fields in one, which implies that all the field names must be unique across the table set.
This leaves the question of why the child tables ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access