> I still do not get why the R4 documentation for Query by attribute
discusses how a # query will function if the "Map null
> to blank” checkbox is or is not checked it the checkbox does not exist
for an object field.
John, random thought: Object fields aren't supported in 4D's SQL. So any
it's probably an omission in the structure editor.
by default the property is on,
but you can change the field type to text or whatever, disable it, and switch
back to object.
it sounds crazy but it should work.
> 2017/10/10 14:52、John Baughman via 4D_Tech <4d_tech@lists.4D.com> のメール：
>
> I
Keisuke,
No sure I understand your response.
I am working in R4 and was trying to query on an object field and
thought I could leave the field undefined using Query By Attribute. Not so, but
I am content with initializing all the records with an object so the the query
works
the "map null to blank" property was originally introduced in v11,
as a way to tell SQL that pre-existing NULLs
(which could typically be created by adding fields)
should not be considered NULLs in SQL.
otherwise, as far as SQL is concerned,
NULLs should never be mapped to blanks.
(that is why the
The documentation for Query by Attribute discusses at length how a # query
performs with or without the Map NULL values to blank values checked.
I do not see this checkbox in the field Explorer window for an Object field.
Am I missing something here? It is there for other types of fields but
5 matches
Mail list logo
