|Home | Concepts | API | Samples|
|Concepts > Versioning > Basic Principles|
To a client application, versioned data appears much the same as unversioned data: versioned tables and feature classes look like the unversioned tables and feature
classes. A table or feature class viewed in one version will contain a certain number of rows, and the same table or feature class in another version may contain a
different number of rows, giving the impression that each version is a separate copy of the data.
These delta tables record any changes (new, modified, or deleted records) made to that table or feature class at each state of the database. To correctly represent each database version, these tables are queried, in conjunction with the Versions and State_Lineages tables, to identify which change was made at which database state. A version will then return a seamless view of the data that takes into account the original state of the data plus any changes.