Skip to content

fix: schema method should use postgres method directly #1082

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

Merged
merged 1 commit into from
Mar 24, 2025

Conversation

silentworks
Copy link
Contributor

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Schema method was being cached and calling the wrong schema each call

What is the new behavior?

Schema method is no longer being cached and calls the correct schema each call

Additional context

Add any other context or screenshots.

@silentworks silentworks requested a review from grdsdev March 23, 2025 12:23
@coveralls
Copy link

Pull Request Test Coverage Report for Build 14018912240

Details

  • 1 of 2 (50.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.7%) to 85.823%

Changes Missing Coverage Covered Lines Changed/Added Lines %
supabase/_sync/client.py 0 1 0.0%
Totals Coverage Status
Change from base Build 14018756108: 0.7%
Covered Lines: 339
Relevant Lines: 395

💛 - Coveralls

@silentworks silentworks enabled auto-merge (squash) March 23, 2025 13:01
@silentworks silentworks merged commit b992324 into main Mar 24, 2025
11 checks passed
@silentworks silentworks deleted the silentwork/fix-schema-method branch March 24, 2025 14:46
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