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

Allow storing numeric data types #112

Open
kzarzycki opened this issue Oct 1, 2016 · 0 comments
Open

Allow storing numeric data types #112

kzarzycki opened this issue Oct 1, 2016 · 0 comments

Comments

@kzarzycki
Copy link

I would like to store numeric fields in TrailDB, e.g. "price of the item bought by user" and be able to range filter events based on that, like "find user purchases of items which cost > 100$" .

Of course currently TrailDB allows you to store numeric data, but it considers it a string. That makes storage inefficient (with dictionary encoding). Additionally, filtering the data based on range requires first decoding the values from stored items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants