Skip to content

Don't open multiple connections on schema update #1924

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

Closed
wants to merge 2 commits into from

Conversation

DavideD
Copy link
Member

@DavideD DavideD commented May 27, 2024

Fix #1909

This should prevent opening multiple connections during schema migration.
I need to figure out how to test it though (I've only checked manually).

@DavideD DavideD force-pushed the 1909 branch 2 times, most recently from f05cc14 to 6d6f334 Compare May 27, 2024 12:18
@DavideD DavideD changed the title [DRAFT] Don't open multiple connection on schema update Don't open multiple connection on schema update May 27, 2024
@DavideD DavideD assigned DavideD and yrodiere and unassigned DavideD May 27, 2024
@DavideD DavideD changed the title Don't open multiple connection on schema update Don't open multiple connections on schema update May 27, 2024
@DavideD DavideD requested a review from yrodiere May 27, 2024 12:29
@DavideD DavideD marked this pull request as ready for review May 27, 2024 12:30
@DavideD
Copy link
Member Author

DavideD commented May 27, 2024

I'm not going to merge this for now, I think there's something to change related to the API that and I need to think more about it

@DavideD DavideD closed this May 27, 2024
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.

Acquisition of multiple connections for schema management
2 participants