Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Add support for SQLAlchemy 1.4 #177
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
feat: Add support for SQLAlchemy 1.4 #177
Changes from all commits
0fc64fa
bfdda68
41cb2dd
631c060
aa85cb9
c7da257
3916239
46b30b4
36a0033
d079fbe
7e60691
4a1bafd
e07b1f0
656af06
a085db6
681ea47
cde5bf8
76cf078
ee46a1e
62432a3
a54b946
1320f32
4f098fd
2c76342
68f9043
be1e215
39f1955
9e266f2
fa84c95
b01d2ce
dc91449
3743abe
dcc7e45
163d031
c47a83d
9444c20
30c8ed7
0ef4909
99629cf
5e6e48d
83feb1e
896a082
497cc90
7e5399a
e48dd58
395a2d4
07af7ef
ea99108
7039f05
0f2d315
9db1e3b
50e3448
f449c5e
d000075
190136e
acdd4d2
3e73a0a
4c6d72d
349269f
717dd77
7ba7813
c22565e
dc246ae
b914ee3
a7e49e9
53883d5
5b1e77e
beaf0b6
8236d5b
8e41b4d
e9c5175
7835d2c
dda37eb
b774f79
7a31d12
78be3cf
297e532
0adebe1
21121e9
b942a61
4aeb0db
a8add9e
04aaee4
0e081a0
6fe196e
67733fd
725c5d5
cb56463
58c3d55
d8e464a
fabd4c6
5cf4009
33642ff
401ad3b
2313f54
7e57563
534a819
32f6b95
c762a9c
492530b
15ba275
a65bd1a
ab873aa
b1224c3
ba21553
445832e
2ef50bd
5cd127a
ed81f2c
28e4f40
9616813
0b1e85e
00d61f4
c58f5f1
7e826e1
b469f3f
c021366
5af39be
a2e92a3
e85558b
c683b52
b7bc62b
69c1d40
62d8df2
b2ac135
e5e9786
9aa57c2
250332b
9963202
c280c1f
7625e61
988a0e9
410b9ac
0b8e3f0
fa303d7
1589a5e
bbb0b54
0d2169a
89036ce
899300b
e9a1378
5ce7507
3c4c8c7
3667869
87f2846
dc28277
159fd18
05528af
2db2dd4
8ea13de
ae03721
486873b
a897d60
6e4d5d6
708f5db
eeaae87
ce6181f
877106b
2a25233
6dbf222
db7a04f
ddd3399
e063e3e
7530acf
4d99090
6b2a6b6
bc40df2
ec4961c
16e302d
6793760
1e11ce2
ff35acf
b4c3c23
18ebe26
fbbd563
a103ae8
5809a9c
b882818
7ee98be
4728f5e
bd9d688
0fa700f
43fe9b8
5eae34c
1f1a510
c0b742d
cabffb1
fff1811
d5251ce
0b7e193
ff3b4fc
d3f5b7c
de6a514
a83fc85
c11a3c3
634b824
6a53bcb
fd65861
dc74972
863ef00
d2eefa4
00ea3ab
d47a57b
78c3056
8e5cea6
2d42d71
7a802ee
80f1ee9
7596f6d
dc21cbf
d17c2f0
ff11a31
08c781c
e06fac2
ce87a54
da3ce60
26c16a7
6996562
55ecde6
9ae173a
d0edaea
2c5d992
070814e
0fc9db6
64206c0
41edaa5
738faa0
4d80d23
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
When i worked on this change, i was a bit worried about the consequences of users passing "inline" as a named parameter.
AFAIR - it was removed from SQLA right?
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 wasn't thinking about users passing
inline
. :)Yes, SQLA removed it in 1.4. I want this code to work with earlier versions and since we're only using
statement
, I'm just passing the later arguments along.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.
why Is that different than 3.9 constraint on SQLA?
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.
To make sure we run with 1.3 in some of the unit tests.
There are code paths needed for 1.3 that aren't exercised with 1.4. Without this, we wouldn't have the required 100% test coverage (and wouldn't be testing with 1.3).