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

Decide on an approach to refreshing table contents #2

Open
deoren opened this issue Jul 29, 2018 · 1 comment
Open

Decide on an approach to refreshing table contents #2

deoren opened this issue Jul 29, 2018 · 1 comment
Assignees
Labels
question Further information is requested
Milestone

Comments

@deoren
Copy link
Contributor

deoren commented Jul 29, 2018

In the SQLite database I'll need to decide whether the main script handles dropping existing tables or just the contents of the tables.

The current version I'm working with handles dropping table contents only and doesn't take into account schema changes, either at MySQL or SQLite level. Is this intended, with the goal of having a migration script handle updating table structure or should we just nuke the entire file on each run?

@deoren deoren added the question Further information is requested label Jul 29, 2018
@deoren deoren self-assigned this Jul 29, 2018
@deoren
Copy link
Contributor Author

deoren commented Jul 29, 2018

There is probably good reason to not nuke the actual file: permissions on the file may be greater than the surrounding directory, thus if we nuke the file we may be unable to recreate the file, but if we nuke the tables within the file we leave the granted permissions on the file intact.

@deoren deoren added this to the Future milestone Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant