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

Sync django query and postgres query #653

Merged

Conversation

GreatBahram
Copy link
Contributor

The upgrade documentation recommends a multi-stage upgrade, during which some records might have a changes field that is no longer empty. This case is handled in the Django query but not in the Postgres one.

Additionally, if there are many records and the upgrade fails, we are returned to the initial state, which is not ideal.

This change should take care of these problems 🤞

Copy link

codecov bot commented Jun 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.29%. Comparing base (5289482) to head (904edb0).
Report is 16 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #653      +/-   ##
==========================================
+ Coverage   95.21%   95.29%   +0.07%     
==========================================
  Files          31       31              
  Lines        1025     1041      +16     
==========================================
+ Hits          976      992      +16     
  Misses         49       49              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@hramezani
Copy link
Member

Thanks @GreatBahram

@hramezani hramezani merged commit 5bb701d into jazzband:master Jun 12, 2024
8 checks passed
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