TOYS does not show the columns, constraints, indexes and triggers for tables being created or dropped. Why?
One of the most fundamental problems when comparing database structures is being overloaded with detail which is distracting and irrelevant. TOYS attempts to minimize this “noise”. It tries to show you only the real differences. If a table is dropped from your reference schema then of course its sub-components are dropped. Who wants to be told that each of it’s columns, constraints, indexes, triggers, etc. are absent? The Oracle catalogs present meta-data in tabular form. Given data in this structure, it is a lot easier to report all this irrelevant garbage then to filter it. Many other schema compare tools take this simpler approach. When developing TOYS, we chose to use an “intelligent” approach to comparing schema and to present you with a consise picture of the true differences. As such, TOYS treats a schema as a hierachy of objects and not as unrelated collections of objects. Using this hierarchical approach, TOYS considers table columns, indexes, constraints and triggers to be ch
Related Questions
- Which tables and columns in the schema contain the data found in the Population Diversity section of the refSNP Cluster Report?
- TOYS does not show the columns, constraints, indexes and triggers for tables being created or dropped. Why?
- How do I quickly encrypt columns in very large tables with billions of rows?
