Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve normalization handling #74

Open
medikoo opened this issue Sep 29, 2016 · 0 comments
Open

Improve normalization handling #74

medikoo opened this issue Sep 29, 2016 · 0 comments
Assignees

Comments

@medikoo
Copy link
Owner

medikoo commented Sep 29, 2016

Currently when we save value at given property, flow is as following:

dbjs-normalization

And then at value retrieval again normalization step is considered, (as between store and get the model could have been changed).

Still that appears problematic as we loose precision. e.g. if at some point we want to increase detail of property characteristics. Initially we wanted to save integers, then we decided we need two fraction digits, then we're not able to retrieve that fraction detail from already saved properties as they were already stored as normalized to integers.

Solution would be to introduce only base level normalization at value store (which means we will use normalize from base type, so e.g. will turn strings to numbers for numeric types, but we will not affect number value), and full (corresponding to given property type and definition) normalization at value retrieval.

@medikoo medikoo self-assigned this Sep 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant