-
-
Notifications
You must be signed in to change notification settings - Fork 49
added support for sqlalchemy2 #120
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
Conversation
did you mean to close this? |
I closed this because the tests were broken and I have no idea at the moment how to arrange the tests against the different sqlalchemy versions. Sorry for that. |
Then best to leave the PR open and we can work together to fix tests. Looks to me like a warning from usage of |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #120 +/- ##
===========================================
- Coverage 100.00% 99.25% -0.75%
===========================================
Files 4 7 +3
Lines 279 537 +258
Branches 38 75 +37
===========================================
+ Hits 279 533 +254
- Misses 0 2 +2
- Partials 0 2 +2
Continue to review full report at Codecov.
|
I added support for models defined using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with the result, but I think there's a more elegant way to do this.
great, thanks so much. |
Hi Samuel,
I think you missed my question about "deferred" fields. Should we display
it as "<deferred>" or just skip such fields?
Thanks!
WBR
Victor
…On Mon, 6 Feb 2023 at 17:23, Samuel Colvin ***@***.***> wrote:
great, thanks so much.
—
Reply to this email directly, view it on GitHub
<#120 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBRL4C3A7L6QMSK3Y6TT33WWEQONANCNFSM6AAAAAAUNRDV4I>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Hi Samuel,
I noticed that the debug stopped working on sqlalchemy 2.0. Here is the PR that solves it for me.
Thanks!