knobit.org

I3 (1 points)

edu:Question

https://knobit.org/id/task/dm-physical-postgres/I3

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dm-physical-postgres/I3
rdfs:labelI3 (1 points) en
schema:hasPartdm-physical-postgres I3: card transactions in clone tables by year
schema:identifierI3
schema:position7
schema:textClone tables: card_transaction_2025 and card_transaction_2026 split one entity by year; acquirer_reference_number is unique in each but not across both, chargeback cannot declare a foreign key, and every question across years needs a union. Merged into one card_transaction table, optionally range-partitioned on transaction_at in physical_options, with a real foreign key from chargeback. An answer that partitions it says that PostgreSQL requires the partition key in every unique constraint, so uniqueness of the acquirer reference across partitions is either keyed with transaction_at or checked by a DQ rule. en

Used by

has questionRetail banking servicing schema on PostgreSQL (transactional physical design anomaly skills)
schema:isPartOfdm-physical-postgres I3: card transactions in clone tables by year