Should I implement a read database normalization (using join tables) or should I use the ENUM type for static or dynamic data?
For example:
I have a table USER
with a user_status
. Should I create a table a status
table or I create a ENUM list with the statuses?
Thanks G
A relation is in 1NF if it contains an atomic value. 2NF. A relation will be in 2NF if it is in 1NF and all non-key attributes are fully functional dependent on the primary key. 3NF. A relation will be in 3NF if it is in 2NF and no transition dependency exists.
First Normal Form (1 NF) Second Normal Form (2 NF) Third Normal Form (3 NF) Boyce Codd Normal Form or Fourth Normal Form ( BCNF or 4 NF)
Normalization is the process to eliminate data redundancy and enhance data integrity in the table. Normalization also helps to organize the data in the database. It is a multi-step process that sets the data into tabular form and removes the duplicated data from the relational tables.
IMHO, the enum extension makes it much easier to embed semantics into a table and also improves efficiency by:
The only downsides I am aware of is
HTH
C.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With