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

support sqla 2.0 #89

Merged
merged 4 commits into from
Nov 7, 2023
Merged

support sqla 2.0 #89

merged 4 commits into from
Nov 7, 2023

Conversation

indiVar0508
Copy link
Contributor

No description provided.

@indiVar0508 indiVar0508 linked an issue Aug 10, 2023 that may be closed by this pull request
@indiVar0508 indiVar0508 force-pushed the add_72 branch 5 times, most recently from 99055f4 to 5a42792 Compare August 10, 2023 13:42
@indiVar0508 indiVar0508 marked this pull request as draft September 19, 2023 04:13
@indiVar0508 indiVar0508 force-pushed the add_72 branch 4 times, most recently from 0ab6e49 to 4d2b7cf Compare October 20, 2023 10:02
@coveralls
Copy link

coveralls commented Oct 20, 2023

Pull Request Test Coverage Report for Build 6779158147

Warning: This coverage report may be inaccurate.

We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

  • 106 of 107 (99.07%) changed or added relevant lines in 28 files are covered.
  • 42 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.8%) to 96.916%

Changes Missing Coverage Covered Lines Changed/Added Lines %
tests/test_i18n.py 2 3 66.67%
Files with Coverage Reduction New Missed Lines %
tests/test_i18n.py 42 26.15%
Totals Coverage Status
Change from base Build 6745145883: -0.8%
Covered Lines: 5007
Relevant Lines: 5097

💛 - Coveralls

@indiVar0508 indiVar0508 marked this pull request as ready for review October 20, 2023 10:28
@AbdealiLoKo AbdealiLoKo enabled auto-merge (rebase) November 5, 2023 12:49
ran all tests with flag SQLA_20_WARNING=1 and resolved all warning
broadly below mentioned warnings are resolved
1. select query syntax changed to leverage positional args and
   select_from
2. use session.get_transaction() instead of session.transaction
3. use row._mapping[..] instead of row[..] to keep it compatible
   with sqla2.0
4. use sa.text() for string based queries
5. use session.get instead of session.Query.get(
6. import declarative_base from sa.orm instead of
   sa.ext.declarative_base
7. use connection.begin() to execute queries from metadata
8. use versions.all()[-1] instead of versions[-1] as negative
   indexing support is deprecated
9. cascade_backref support is to be dropped from 2.0 so add
   object before merging
10. removed pin for <2.0
11. use sa.orm.Mapper instead of sa.orm.mapper
12. concreteInheritedProperty doesn't have active_history
    used what is done for sqla-continuum
13. use savepoint to rollback
ref: kvesteri/sqlalchemy-utils#719

there is some issue b/w sqla-utils and sqla==2.0.22 so excuding sqla>=2.0.22
for now.

`TypeError: __init__() missing 1 required positional argument: 'dispatch'`
indiVar0508 and others added 2 commits November 7, 2023 07:47
from sqla 2.0, it will not explicitly add start=1 on queries
generated for sequence which impacts mssql queries, so passing
start=1 for all DB(s)
ref: https://docs.sqlalchemy.org/en/20/dialects/mssql.html#sequence-support
@AbdealiLoKo AbdealiLoKo merged commit 5afc0a3 into master Nov 7, 2023
21 checks passed
@AbdealiLoKo AbdealiLoKo deleted the add_72 branch November 7, 2023 02:26
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.

Need to Check Compatibility with SQLA-2.0
3 participants