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.

Sign up for GitHub

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

Jump to bottom

Checksums are not preserved when files are moved #4034

Closed
ckamm opened this issue Oct 29, 2015 · 1 comment
Closed

Checksums are not preserved when files are moved #4034

ckamm opened this issue Oct 29, 2015 · 1 comment
Assignees
@ckamm
Labels
ReadyToTest QA, please validate the fix/enhancement type:bug
Milestone
2.1

Comments

@ckamm
Copy link
Contributor

ckamm commented Oct 29, 2015

I need to carefully look at all setFileRecord calls and check whether they handle checksums correctly...
@ckamm ckamm added the type:bug label Oct 29, 2015
@ckamm ckamm self-assigned this Oct 29, 2015
@ckamm ckamm modified the milestones: 2.2-next, 2.1-next Oct 29, 2015
@guruz guruz mentioned this issue Nov 3, 2015
Closed
ckamm added a commit that referenced this issue Nov 10, 2015
@ckamm
Checksums: Treat more carefully in db #4034
17dd199 
In particular, preserve them on local rename or remote move.
@ckamm ckamm added the ReadyToTest QA, please validate the fix/enhancement label Nov 10, 2015
@ckamm
Copy link
Contributor Author

ckamm commented Nov 10, 2015

You can test this by using sqlitebrowser on the DB. Set a checksum for a file, rename it, check that the checksum moved along with the file.

@danimo danimo closed this as completed Jan 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ckamm ckamm

Labels
ReadyToTest QA, please validate the fix/enhancement type:bug
Projects
None yet
Milestone
2.1
Development

No branches or pull requests
2 participants
@ckamm @danimo