Skip to content

chore(deps): fix the compatibility issue introduced by SQLAlchemy 2.0.38 #989

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
Feb 12, 2025

Conversation

behnazh-w
Copy link
Member

@behnazh-w behnazh-w commented Feb 12, 2025

This PR refactors the view creation process to avoid using internal SQLAlchemy functions, ensuring the implementation relies solely on the officially supported functions and best practices.

Additionally, it enhances the docstrings for the related functions to provide clearer and more detailed explanations.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Feb 12, 2025
@behnazh-w behnazh-w force-pushed the behnazh/fix-sql-alchemy-issue branch from 069171d to acca567 Compare February 12, 2025 01:47
@behnazh-w behnazh-w marked this pull request as ready for review February 12, 2025 01:50
@behnazh-w behnazh-w requested a review from tromai as a code owner February 12, 2025 01:50
@behnazh-w behnazh-w requested a review from benmss February 12, 2025 01:50
@behnazh-w behnazh-w merged commit 58b1a8b into staging Feb 12, 2025
10 checks passed
@behnazh-w behnazh-w deleted the behnazh/fix-sql-alchemy-issue branch March 10, 2025 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants