-
Notifications
You must be signed in to change notification settings - Fork 127
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
bug in version 1.3.13: sqlalchemy.exc.DataError: (psycopg2.errors.InvalidTextRepresentation) invalid input syntax for type bigint: #316
Comments
DEBUG log
a string type value is set for |
xg1990
added a commit
to xg1990/sqlalchemy-continuum
that referenced
this issue
Oct 31, 2022
This is exactly the issue I have summarized in #149 (comment) @marksteward please revert this commit 🐈 |
anthraxx
added a commit
to anthraxx/sqlalchemy-continuum
that referenced
this issue
Jan 3, 2023
This reverts commit 7eda527. This was actually a misinterpretation of the API: The API expects get_id() to be a unique string, that may or may not be an integer. This feature is only used to uniquely identify the user, but its not the same as the user's primary key. https://flask-login.readthedocs.io/en/latest/#your-user-class Please take a note on how get_id() is expected to behave on this feature of flask-login: https://flask-login.readthedocs.io/en/latest/#alternative-tokens This means it can return any arbitrary string to identify the user which can be swapped to any other value to invalidate all sessions. This explicitly states that it is not the same as the user's primary id which is also used as foreign key on the table. sqlalchemy-continuum's transaction tables reference the user with a foreign key of the actual id. If a downstream application uses the alternative-tokens feature as described by the flask-login documentation, this breaks horribly as sqlalchemy-continuum will then try to insert an arbitrary unique string of the user as the foreign key to reference the user in the user table. Fixes kvesteri#316 Caused by kvesteri#149
marksteward
added a commit
that referenced
this issue
Jan 4, 2023
Fixed in 1.3.14, sorry for not picking this up before! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem described below only happens with
SQLAlchemy-Continuum-1.3.13
Error Stack:
The above exception was the direct cause of the following exception:
The text was updated successfully, but these errors were encountered: