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
Currently the ORM doesn’t check data consistency very thoroughly. It’s possible to manually (not through the API) to create a host that then causes errors when further manipulated. An example can be that the facts field doesn’t default to an empty dictionary on safe etc.
It would be good to take some measures that would make the data more consistent and the app then durable:
Check the data validity and consistency on save to the database. Do not limit the validation checks only to API requests.
Set some reasonable default values in a unified ways, e.g. that the facts and system_profile_facts store "{}" instead of "null".
In general, the application is not very friendly to scripting, ad-hoc usages or debugging. Any non-API scripts then become a possibly deadly tool that can botch the database if the developer doesn’t remember all necessary constrains.
The text was updated successfully, but these errors were encountered:
Glutexo
changed the title
Improve that data validation and consistency
Improve data validation and consistency
May 20, 2019
Currently the ORM doesn’t check data consistency very thoroughly. It’s possible to manually (not through the API) to create a host that then causes errors when further manipulated. An example can be that the facts field doesn’t default to an empty dictionary on safe etc.
It would be good to take some measures that would make the data more consistent and the app then durable:
"{}"
instead of"null"
.In general, the application is not very friendly to scripting, ad-hoc usages or debugging. Any non-API scripts then become a possibly deadly tool that can botch the database if the developer doesn’t remember all necessary constrains.
The text was updated successfully, but these errors were encountered: