Point in time without a zone, business date with a clock (generated DDL)
https://knobit.org/id/knobit/K-818
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 |
| assessment criterion | Flags the deficient case and passes the acceptable one. Deficient: `created_at TIMESTAMP` with no zone on `dim_account`, written by jobs in two regions. And `payment_value_date` as a `TIMESTAMP`, so `= DATE '2026-03-31'` matches none of the rows loaded at 23:30 Acceptable: `TIMESTAMP WITH TIME ZONE` for event times, or UTC with the convention stated in the column `comment` and nowhere else; `DATE` for `payment_value_date`, `loan_maturity_date` and `valid_from_date`/`valid_to_date`, as the sample model has them en |
| assessment method | skill-tests task: Generated DDL review, Postgres and Snowflake (DDL review skills) en |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:identifier | K-818 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Review checklist 05-ddl, row 18; ISO 8601; ISO 9075 en |
| expected result | A finding that names the defective generated DDL element and the defect en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-modelling/08-ddl/18 |
| rdfs:label | Point in time without a zone, business date with a clock (generated DDL) en |
| schema:creativeWorkStatus | superseded |
| schema:isPartOf | Data modelling (DAMA-DMBOK2) |
| schema:supersededBy | Recognises a time zone dropped from a timestamp |
| schema:supersededBy | Recognises a business date stored with a time of day |
| skos:definition | Two mirror-image defects. An event timestamp with no offset is ambiguous twice a year and incomparable across a bank that books in more than one zone. A business date — value date, booking date, maturity date, due date — stored as a timestamp invites a time component nobody means and makes date equality quietly fail. en |
| skos:prefLabel | Point in time without a zone, business date with a clock (generated DDL) en |
| target object | generated DDL en |