Database design: storing delimited rows in a database is bad

I worked on projects before they store fields in a comma or string separated by commas, as a field that can be parameters or something similar. I was wondering if this would be considered a poor database design and always need to use relational tables or is it sometimes acceptable to store data this way?

+3
source share
14 answers

This is usually a bad idea .

However, there is a balance between normalization and performance.

-, , , , .

+10

. , , . , fullname, - ..

, ..

, , , firstname lastName.

, , , . , .

+7

:

  • , -/ . , , , , .

  • , . , Python pickle , , , .

+1

, , , . Drupal, Wordpress .. .

+1

- - , , ? , ?

0

, ( ). . , , ... ?

0

. . :

, , ( )

() . , , .

0

.

, :

abc | 123,456,789
def | 123
ghi | 123

:

1 | abc | 123
2 | abc | 456
3 | def | 123
4 | ghi | 123
5 | abc | 789
0

, " ". db , . , , , , - .

, , , . - , u + x, , .

0

. , SOAP- . . , .

0

, , , . , .

, . . JSON , "", , JSON. "", , , . , .

"version_id" , .

. , .

0

, , , , .

, , - " ", , , . , (, , ) . , , , , , "denormalised for performance".

0

, , , . , XML , -, .

, , .

0

, , - , . , , , , - , , . , - , - , , , , , , , , , , .

0

Source: https://habr.com/ru/post/1722152/


All Articles