Changes between Version 6 and Version 7 of TracDev/ScratchPad/DataModels

Timestamp:

Apr 16, 2018, 11:11:50 AM (6 years ago)

Author:

Ryan J Ollos

Comment:

Document behavior dicussed in comment:18:ticket:12029.

TracDev/ScratchPad/DataModels

@@ -9 +9 @@
 === Standardize missing values
 
-For tickets, when a field is unset the database value is set to `None` / `NULL` (#11018). When retrieving `NULL` values from the database, we get `None` in Python, and the empty string is returned from the model using the special value [apidoc:api/trac_util_text#trac.util.text.empty empty]. See e.g. what we do for  [source:trunk/trac/ticket/model.py@11111:127,137#L110 ticket fields]. The pattern could be extended to other model classes, and even the `Ticket` model should be reviewed to ensure that all fields follow the pattern.
+For tickets, when a field is unset the database value is set to `None` / `NULL` (#11018). When retrieving `NULL` values from the database, we get `None` in Python, and the value returned from the model depends on the field type:
+* For text fields, the empty string is returned from the model using the special value [apidoc:api/trac_util_text#trac.util.text.empty empty]. See e.g. what we do for  [source:trunk/trac/ticket/model.py@11111:127,137#L110 ticket fields].
+* For time fields, `None` is returned.
+
+The pattern could be extended to other model classes, and even the `Ticket` model should be reviewed to ensure that all fields follow the pattern.
 
 === `NOT NULL` columns