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

Transition to a Hybrid SQLite database and hashmap table data structure design for unit storage and processing. #4

Open
isaaclafrance opened this issue Jan 29, 2017 · 2 comments
Assignees

Comments

@isaaclafrance
Copy link
Owner

isaaclafrance commented Jan 29, 2017

  • The sql database will allow for efficient and fast retrieval of unit names based on various search criteria. Then once the unit name is obtained it will subsequently be used with a hash map to get the corresponding unit object.
@isaaclafrance isaaclafrance self-assigned this Jan 29, 2017
@isaaclafrance isaaclafrance changed the title Transition to a SQLite database design for unit storage rather than a hash table data structure. Transition to a Hybrid SQLite database and hash table data structure design for unit storage and processing. Mar 7, 2017
@isaaclafrance isaaclafrance changed the title Transition to a Hybrid SQLite database and hash table data structure design for unit storage and processing. Transition to a Hybrid SQLite database and hashmap table data structure design for unit storage and processing. Mar 7, 2017
@isaaclafrance
Copy link
Owner Author

Decided against using sql all together. The application infrastructure is too heavily dependent on the hash map data structure and so a change to sql would require a major alteration in how things operate. Moreover, the existing data structure already sufficiently satisfies the need of the application.

@isaaclafrance
Copy link
Owner Author

After refactoring, reconsidered using sql on a more limited scale to store and retrieve only dynamic units and prefixes.

@isaaclafrance isaaclafrance reopened this Apr 16, 2017
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