@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dm-ddl-review-deploy/I4> a edu:Question ;
    rdfs:label "I4 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    schema:hasPart <https://knobit.org/id/register/data-modelling#I-824> ;
    schema:identifier "I4" ;
    schema:position 7 ;
    schema:text "A type meaning something else per engine, 1 each: (a) dim_date.is_business_day BOOLEAN renders as BOOLEAN on Postgres and Databricks, BIT on SQL Server, NUMBER(1) on Oracle and TINYINT(1) on MySQL, so the calendar feed's 2 (half business day) is rejected on Postgres, silently becomes 1 on SQL Server and is stored as 2 on Oracle and MySQL - four meanings of one column; (b) the fix is in the model: a check constraint for the 0/1 domain on the engines without a boolean, and the half day raised as a domain question (a business-day type code, or a decision that it maps to 0 or 1) rather than left to each engine."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-modelling#I-824> rdfs:label "dm-ddl-review-deploy I4: BOOLEAN meaning four things on five engines"@en .

