Timeline for User's comment field on a row in relational databases
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 24, 2022 at 10:00 | comment | added | Doc Brown | @kiwiron: quite the opposite. If you allow NULL values and empty strings in a column, but both are semantically equal, the correct query will have to be COMMENT IS NULL OR COMMENT='', or ISNULL(COMMENT,'')=''. That is definitely more complicated than COMMENT='', which is sufficient with the NOT NULL constraint in place. | |
| Aug 24, 2022 at 6:43 | history | edited | Doc Brown | CC BY-SA 4.0 | added 19 characters in body |
| Aug 24, 2022 at 6:40 | comment | added | kiwiron | This is a first - I normally agree with @DocBrown answers. I agree with the first answer - if there is no comment then the field should be null. Otherwise standard database functions like COUNT will return wrong results and other queries are complicated compared with "COMMENT IS NULL". | |
| Aug 24, 2022 at 5:37 | history | edited | Doc Brown | CC BY-SA 4.0 | added 24 characters in body |
| Aug 24, 2022 at 4:34 | history | answered | Doc Brown | CC BY-SA 4.0 |