Recognises a lossy or unconstrained vertical split
https://knobit.org/id/knobit/K-604
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: `account` and `account_interest_terms`, the second with its own surrogate and joined on the product code: two accounts on one product give four rows. Or `account_interest_terms.account_id` with an FK but no unique constraint Acceptable: Both tables keyed on `account_id`; in the extension the primary key is also the foreign key, so one-to-one is enforced; whether the extension is optional is stated 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-604 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Review checklist 04-physical, row 4; Heath 1971; Rissanen 1977; S&W 12.6; E&N 17.7 en |
| depends on knobit | Recognises a lossy decomposition |
| expected result | The split and its missing key or constraint en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-modelling/06-physical/04 |
| rdfs:label | Recognises a lossy or unconstrained vertical split en |
| schema:creativeWorkStatus | accepted |
| schema:isPartOf | Data modelling (DAMA-DMBOK2) |
| skos:altLabel | Lossy or unconstrained vertical split (physical model) en |
| skos:definition | One entity split into two tables for width or access, where the tables do not share the key, or the one-to-one relationship between them is not enforced. Joining back produces rows that never existed, or one row gets two extensions. A dependency spanning both parts has no key to enforce it. en |
| skos:prefLabel | Recognises a lossy or unconstrained vertical split en |
| target object | table split without shared key or enforced one-to-one en |
Used by
| includes knobit | Designs a physical data model for the target platform without introducing anomalies |
|---|---|
| requires knobit | Design the physical data model |