Object fields and Map Null values

Hello,

Going back to v17.0 the docs state this:

http://livedoc.4d.com/4D-Language-Reference-17-R3/Queries/QUERY-BY-ATTRIBUTE.301-3906718.en.html
Using the # operator (support for Null values)
Queries by attribute using the “#” operator can have different results depending on whether or not the Map NULL values to blank values property is checked for the object field:
Map NULL values to blank values property checked (default option, recommended in most cases).

However in the database structure window, when looking at the Inspector of an Object field, the “Map NULL values to blank values” checkbox is not present. Is there no option to turn it on or off for Object fields? What is its new permanent setting?

Using v17.232154 64-bit & macOS 10.14.2

Thanks

the classic language did not need to care about NULL because a field was always given the default value of “”, 0, 00/00/00, 00:00:00, False, empty picture, empty BLOB.

see “https://doc.4d.com/4Dv17/4D/17/Field-properties.300-3743586.en.htmlMap NULL values to blank values>”

the property was introduced in v11, because NULL must be available for SQL, yet not all applications need SQL.

Null (notice the lower case), on the other hand, has nothing to do with SQL.

Null is a perfectly valid object value/state and it would be inappropriate to equate it with empty value under any circumstances.

as a side note, the =/# operator in 4D (not query in particular, but general comparison) does equate Null with Undefined for convenience.

during last year’s summit presentation it was explained that differentiating the two would just make matters more complicated without much benefit.

also,

until now it was not possible to set an object field to NULL using SET FIELD VALUE NULL,

(as opposed to $obj:=Null)

but that issue is solved in 17r4 (https://bugs.4d.fr/fixedbugslist?branch=17_R4ACI0098769>)

Right. I was seeing “Queries by attribute using the “#” operator can have different results depending on whether or not the Map NULL values to blank values property is checked for the object field:” as referring to fields of type Object, and was going to explore the way it would affect queries on the Object type…
Thanks,