Home › GATE CSE › computerscience › Database Management Systems › Per the Methodist notes' guidance, when should d…
Per the Methodist notes' guidance, when should designers stop at 3NF rather than pushing all the way to BCNF?
Awhen the relation has only a single candidate key
Bwhen the engine is MySQL rather than PostgreSQL
Cwhen pushing to BCNF would lose dependency preservation
Dwhen the relation has more than ten attributes
Answer & Solution
Correct answer: C. when pushing to BCNF would lose dependency preservation
BCNF is strictly stronger than 3NF, but enforcing BCNF can require a decomposition that loses the ability to enforce some original FDs on the resulting tables (loses dependency preservation). 3NF always preserves dependencies. The choice trades stricter normal form for keeping constraints enforceable.
Related questions
The main reasons production DBMSs avoid shadow paging in favour of WAL are that shadow pagWhat is the purpose of a Compensation Log Record (CLR) in ARIES?ARIES recovery is structured as exactlyFuzzy checkpoints differ from naive checkpoints byIn standard log-based recovery, the order of operations isAfter a crash, with checkpointing, the recovery system scans the logA complete log record for a write operation includesPer WAL semantics, a transaction is officially committed at the moment