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

Fix TAM handling in update script #7617

Merged
merged 2 commits into from
Jan 24, 2025

Conversation

svenklemm
Copy link
Member

@svenklemm svenklemm commented Jan 23, 2025

The TAM SQL code was not written with update and downgrade scripts
in mind prevents further releases past 2.18.0 due to not splitting
up the parts that need to be part of every update script and those
that can only run once during initial installation.

Disable-check: force-changelog-file
Disable-check: commit-count

Copy link

codecov bot commented Jan 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.28%. Comparing base (59f50f2) to head (ba5e66a).
Report is 710 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7617      +/-   ##
==========================================
+ Coverage   80.06%   82.28%   +2.21%     
==========================================
  Files         190      239      +49     
  Lines       37181    44171    +6990     
  Branches     9450    11104    +1654     
==========================================
+ Hits        29770    36345    +6575     
- Misses       2997     3437     +440     
+ Partials     4414     4389      -25     

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

@svenklemm svenklemm force-pushed the update_script_tam branch 18 times, most recently from 4dbcfbc to ea0a368 Compare January 23, 2025 23:23
We need to allow these in the update script as we try to create
an operator class later that is gonna call those functions during
upgrade process.
@svenklemm svenklemm force-pushed the update_script_tam branch 2 times, most recently from fde95ff to ba5e66a Compare January 23, 2025 23:50
The TAM SQL code was not written with update and downgrade scripts
in mind prevents further releases past 2.18.0 due to not splitting
up the parts that need to be part of every update script and those
that can only run once during initial installation.
@svenklemm svenklemm merged commit dc67130 into timescale:main Jan 24, 2025
47 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.

3 participants