Skip to content

Lookup control writes 0 instead of NULL for nullable field #1813

@mkrecek234

Description

@mkrecek234
  • You have any Lookup for a field which is nullable in a Form with a connected Model (e.g. via hasOne reference)
  • You have selected an entry of the Lookup and saved.
  • You then select the empty entry of that Lookup and save again

Result: Atk4/Data tries to store 0, instead of NULL. This is wrong, it has to be NULL.
Sorry can't provide a quick demo, but this should be straightforward.
Funnily, in Dropdown control it works, only in Lookup not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions