You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
canonical facts – validated to be a dictionary with at least one item from a fixed set
system_profile_facts – defaults to an empty dictionary
I don’t think that we need any sophisticated validation logic in the database layer. The fields are still there with their type and nullability is a very basic property of the field. Moreover, non-nullable fields are more performant – faster to index and search. Not being able to insert a record without a value is in my eyes equally important as not being able to insert a value of a wrong type.
The text was updated successfully, but these errors were encountered:
No host’s fields can ever be empty. Still they are declared as NULL. Let’s switch them to NOT NULL. This applies to:
I don’t think that we need any sophisticated validation logic in the database layer. The fields are still there with their type and nullability is a very basic property of the field. Moreover, non-nullable fields are more performant – faster to index and search. Not being able to insert a record without a value is in my eyes equally important as not being able to insert a value of a wrong type.
The text was updated successfully, but these errors were encountered: