chore(deps): bump sqlalchemy from 1.3.24 to 1.4.7#1972
Draft
romain-dartigues wants to merge 8 commits into
Draft
chore(deps): bump sqlalchemy from 1.3.24 to 1.4.7#1972romain-dartigues wants to merge 8 commits into
romain-dartigues wants to merge 8 commits into
Conversation
Trying to adapt to SQLAlchemy breaking changes,
with the first 1.4 version permitted by dependencies:
zope-sqlalchemy==3.1 depends on one of:
sqlalchemy>=1.1,<1.4.0
sqlalchemy>1.4.6
romain-dartigues
marked this pull request as draft
March 23, 2025 18:03
…se use the .scalar_subquery() method to produce a scalar subquery.
…ent(s) "users.user" and FROM element "users.token". Apply join condition(s) between each element to resolve.
…'t adapt type 'Row'
The error:
[SQL: SELECT guidebook.history_metadata.id, guidebook.history_metadata.user_id, guidebook.history_metadata.comment, guidebook.history_metadata.written_at
FROM guidebook.history_metadata
WHERE guidebook.history_metadata.id IN (%(id_1_1)s, %(id_1_2)s)]
[parameters: {'id_1_1': (11,), 'id_1_2': (12,)}]
(Background on this error at: http://sqlalche.me/e/14/f405)
In this case, it is related to:
So this is the psycopg2 driver being given the value (1, ),
a one-element tuple, as a parameter that is ultimately bound to a SQL
string given the way that psycopg2 binds parameters.
psycopg2 seems to just accept tuples and silently flattens them into
their lone element, unless you pass more than one element:
[...]
unfortunately psycopg2 is simply wrong here and your program has been
relying on a driver bug
— sqlalchemy/sqlalchemy#9214 (reply in thread)
…please pass a select() construct explicitly
…ad operation of attribute 'document_id' cannot proceed (Background on this error at: http://sqlalche.me/e/14/bhk3) This is a workaround as I was unable to fix it in another way (either through `sqlalchemy.orm.undefer` or eager.
romain-dartigues
force-pushed
the
pip/sqlalchemy
branch
from
March 27, 2025 10:11
2441f46 to
189f6e0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Trying to adapt to SQLAlchemy breaking changes,
with the first 1.4 version permitted by dependencies:
There are a lot of breaking changes…
Refs: #1966, #1958