I believe it's a joke. However ... if you store a CV as a blob then separately store skills, experiences in a different table --- does that make the db design imperfect?
Yeah, I was thinking about the way how to actually build a non-1NF database. So far my best idea is to store sqlite files as blobs in a different database.
1NF (depending on the definition) has a few subtleties that make it either impossible to avoid in any relational database or almost impossible to enforce!
By impossible to avoid, I mean the basic rectangular shape of a table.
By impossible to enforce, I mean the avoidance of duplicates (without indexes) and NULLs.