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

Don't allow connection to db that is newer than the one we support #1454

Merged

Conversation

jenshnielsen
Copy link
Collaborator

This can happen if you go back to an old git version and is dangerous
as it can result in inconsistent DBs

I suspect this is the reason why the fix in https://github.com/QCoDeS/Qcodes/blob/master/qcodes/dataset/sqlite_base.py#L2524 has been needed, A db has been upgraded and subsequently written to by an older qcodes version

This can happen if you go back to an old git version and is dangerous
as it can result in inconsistent dbs
@codecov
Copy link

codecov bot commented Jan 25, 2019

Codecov Report

Merging #1454 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1454      +/-   ##
==========================================
+ Coverage   73.75%   73.76%   +0.01%     
==========================================
  Files          92       92              
  Lines       10347    10351       +4     
==========================================
+ Hits         7631     7635       +4     
  Misses       2716     2716

@jenshnielsen jenshnielsen merged commit 1c14781 into microsoft:master Jan 25, 2019
@jenshnielsen jenshnielsen deleted the dont_connect_to_newer_Db branch January 25, 2019 15:04
giulioungaretti pushed a commit that referenced this pull request Jan 25, 2019
Merge: 7592b40 cf0e532
Author: Jens Hedegaard Nielsen <[email protected]>

    Merge pull request #1454 from jenshnielsen/dont_connect_to_newer_Db
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

Successfully merging this pull request may close these issues.

2 participants