Skip to content

[fix] Make sqlalchemy 1.1 and 1.2 behave the same. fix #2058#2120

Merged
gazpachoking merged 2 commits intodevelopfrom
series_bug_sqlalchemy2
Apr 11, 2018
Merged

[fix] Make sqlalchemy 1.1 and 1.2 behave the same. fix #2058#2120
gazpachoking merged 2 commits intodevelopfrom
series_bug_sqlalchemy2

Conversation

@gazpachoking
Copy link
Copy Markdown
Member

Motivation for changes:

SQLAlchemy update to 1.2.0 breaks some stuff for us

Detailed changes:

This change in sqlalchemy 1.2 broke our custom comparators for hybrid properties we were using. Since calling 'comparator' method on hybrid properties no longer mutates the property, we have to re-assign the result back to the property name.

Replaces #2119, fixing the issue at the root.

Addressed issues:

@gazpachoking
Copy link
Copy Markdown
Member Author

Codacy, I think you on crack. Nothing is shadowed here, we define a (settable) property, then set that property in __init__.

@gazpachoking gazpachoking merged commit bedf84f into develop Apr 11, 2018
@cvium cvium deleted the series_bug_sqlalchemy2 branch April 11, 2018 05:09
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.

Unhandled error in plugin series: expected string or bytes-like object

1 participant