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

Consider moving sqlite file outside of repository #3366

Closed
dmpetrov opened this issue Feb 19, 2020 · 2 comments
Closed

Consider moving sqlite file outside of repository #3366

dmpetrov opened this issue Feb 19, 2020 · 2 comments
Labels
discussion requires active participation to reach a conclusion

Comments

@dmpetrov
Copy link
Member

I have heard a few times that people don't like the idea of using binary DB files in DVC and storing them in Git repo. One guy even stopped looking at DVC when he realized this (misunderstood, actually) . The other folks think that DVC requires DB and uses sqlite by default.

The misunderstandings are not an issue. However, it makes people think that DVC has a bad design that might introduce bad practices in their workflow and prevents them from using DVC.

To make DVC design decisions clear we can consider moving .dvc/state file (sqlite) outside of repo - somewhere to /var. I understand that it might require some additional work on naming these files properly. Another, easy solution might be a proper file naming like .dvc/ephemeral.state or .dvc/state.tmp.

@dmpetrov dmpetrov added the discussion requires active participation to reach a conclusion label Feb 19, 2020
@efiop
Copy link
Contributor

efiop commented Feb 19, 2020

@dmpetrov Interesting observation! Maybe let's move it to .dvc/tmp/state? We have .dvc/tmp dir already and a using it for some temp files, so maybe that will make them much less noticeable.

@efiop
Copy link
Contributor

efiop commented Apr 22, 2020

Closing in favor of #3666

@efiop efiop closed this as completed Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion requires active participation to reach a conclusion
Projects
None yet
Development

No branches or pull requests

2 participants