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

Database for storing fragments? #16

Closed
Luke-Poeppel opened this issue Nov 15, 2020 · 2 comments
Closed

Database for storing fragments? #16

Luke-Poeppel opened this issue Nov 15, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Luke-Poeppel
Copy link
Owner

Having to use converter.parse on > 130 files each time, for instance, a RatioTree is created seems inefficient. Perhaps it would make more sense to create a decitala.db and prosodic_feet.db instead? The whole package would run much faster.

@Luke-Poeppel Luke-Poeppel added the enhancement New feature or request label Nov 15, 2020
@Luke-Poeppel Luke-Poeppel self-assigned this Nov 15, 2020
@Luke-Poeppel
Copy link
Owner Author

Note: I could still provide all of the files since they're out of copyright and write better documentation for database generation.

@Luke-Poeppel
Copy link
Owner Author

Done in v0.5.0.

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

No branches or pull requests

1 participant