Recognises an entity split into clone tables by value
https://knobit.org/id/knobit/K-605
Also as Turtle · JSON-LD · RDF/XML · AI benchmark on Skilirium
| Context functions | Result evaluation |
|---|---|
| Knobit creation methods | AI generated, human edited |
| Knobit types | Skill |
| LCG purposes | Assessing the learner's knowledge or skill state |
| LCG purposes | Selecting an assessment task or learning activity |
| action verb | Recognises en |
| applies knowledge | Explains vertical and horizontal partitioning of tables |
| assessment criterion | Flags the deficient case and passes the acceptable one. Deficient: `payment_2025`, `payment_2026`; `payment_identifier` unique in each but not across both; `payment_hold` cannot reference "a payment"; a corrected value date moves the payment between tables Acceptable: One `payment` table partitioned by `payment_value_date` in `physical_options`, keys and foreign keys unchanged. Where separate tables are unavoidable (an archive), their predicates are disjoint and written down, and uniqueness across them is a DQ rule en |
| assessment method | skill-tests task: Loan application physical model on Snowflake (physical design anomaly skills) en |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:identifier | K-605 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Review checklist 04-physical, row 5; Karwin, Metadata Tribbles; Date & McGoveran 1994; S&W 12.6 en |
| depends on knobit | Recognises one entity split by value into several |
| expected result | The tables and the value to make a column en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-modelling/06-physical/05 |
| rdfs:label | Recognises an entity split into clone tables by value en |
| schema:creativeWorkStatus | accepted |
| schema:isPartOf | Data modelling (DAMA-DMBOK2) |
| skos:altLabel | Horizontal split into clone tables (physical model) en |
| skos:definition | One entity stored as several tables with the same columns, split by a value: a year, a region, a status. Uniqueness and foreign keys cannot span them, a change to the split value means moving the row, and every question across values needs a union. The physical form of logical row 28. en |
| skos:prefLabel | Recognises an entity split into clone tables by value en |
| target object | clone tables en |
Used by
| includes knobit | Designs a physical data model for the target platform without introducing anomalies |
|---|---|
| requires knobit | Design the physical data model |