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

Ensure that the order how list of trails comes when call trails:store/1 be the same when call trails:all/0. #28

Closed
cabol opened this issue Jul 1, 2015 · 0 comments
Assignees
Labels

Comments

@cabol
Copy link
Contributor

cabol commented Jul 1, 2015

Currently, when trails:store/1 is invoked, list of trails/routes are stored into an ETS table (in a set structure), so it breaks the order how routes comes in the list, and due to this trails:all/0 returns the list in different order.

One option could be use an ordered_set structure for ETS table, BUT will be necessary add an additional argument (for example a consecutive integer) in order that the tree can be sorted in the right way.

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

No branches or pull requests

3 participants