Skip to content
Advertisement

Tag: database-normalization

is it violate 2NF?

My table book PK ID INT pfK langID INT title VARCHAR description MEDIUMTEXT releaseYear YEAR chaptersPrice DOUBLE thumbnail BLOB Where pfk – Primary-Foreign Key; {ID, langID} – PK; chaptersPrice – price of each chapter of book. Example: BookName1: chaptersPrice=2 BookName2: chaptersPrice=3 I think in this table some attributes are functionally dependent on the part of primary key (ID): {ID} ->

What’s best practice for normalisation of DB where a domain table has an “Other” option for free text?

I’m currently in the process of normalising a database for my company and one pattern I’m seeing a lot in this database is using a domain lookup table for a value but also allowing “Other” and storing the results in a separate column. My question is just whether there is perhaps a cleaner way of representing this? For context I’m

Advertisement