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

Generalise two approaches for storing set/map values #56

Open
medikoo opened this issue Feb 22, 2016 · 0 comments
Open

Generalise two approaches for storing set/map values #56

medikoo opened this issue Feb 22, 2016 · 0 comments
Assignees

Comments

@medikoo
Copy link
Owner

medikoo commented Feb 22, 2016

There are two ways:

  1. Store each key/value (in case of map), or each item (in case of set) via separate record
  2. Store full set or map result with one record.

Currently (1) is used for directly operated (not computed) sets and maps, and (2) is used for computed sets.
It'll be great to have an option to use both (1) and (2) for direct and computed data handling in both map and set cases.

@medikoo medikoo self-assigned this Feb 22, 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