I wonder if it is necessary to have NULL in fields without a value or should it be empty?
what's better?
thank
There is a specific argument that you should never allow NULL in your data if you use it to indicate that you do not know what value should be or you simply do not have data, but then use an explicit value in the field to indicate these conditions. Similarly for "empty" fields. However, I think everyone is doing it or has done it and can do it again. NULL has odd comparative properties, so it is always better, if possible, to avoid this and have explicit values for missing data states.
NULL means no data is given, and an empty string may be some valid data.
Thus, using NULL helps you differentiate these two cases.
. , NULL. , , . , - , NULL .
NULL , , , , . , . , , , .
NULLS , , NULLS. NULLS , , "" ( (FIELD)), .
NULL , NULL. , NULL . Autonumber.
Oracle 1980- , VARCHAR ( ) NULL. " ". .
NULL . , .
. , null . unknon , , . , . 0 - , null, . , , null , , . .
, .
Source: https://habr.com/ru/post/1743153/More articles:Local / Dev / Live Deployment - Best Workflow - phpiPhone - detect end of animation - objective-cclass foo; in the header file - c ++Ruby on Rails - автономное программирование - rubyКак заменить foo на foo с помощью PHP и регулярного выражения? - phpFinding a value of a smaller value and swap in php - comparisonWPF docking recommendation - wpfCan I use Catalyst to display images or graphs? - perlASP.NET user role management - c #Transaction isolation level required for secure identity escalation - sqlAll Articles