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
SQLAlchemy accesses attribute table of custom ColumnElement #4142
Comments
Michael Bayer (@zzzeek) wrote: stack trace.....i have to adapt this to real code and run it to see b.c. not provided... |
Michael Bayer (@zzzeek) wrote: anyway, the answer for now is, put table=None, there's no side effect from that. |
Michael Bayer (@zzzeek) wrote: https://gerrit.sqlalchemy.org/#/c/zzzeek/sqlalchemy/+/610/ will test feasibility of a change to prevent user-defined columnelements from being assumed to be table-bound |
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Dmytro Starosud (@dima-starosud) wrote:
@zzzeek Sorry, will attach later. |
Changes by Dmytro Starosud (@dima-starosud):
|
Dmytro Starosud (@dima-starosud) wrote:
@zzzeek Done. |
Michael Bayer (@zzzeek) wrote: Change visit name for ColumnElement No SQLA built-in subclasses ColumnElement without specifying Fixes: #4142 → 5e8396a |
Changes by Michael Bayer (@zzzeek):
|
Michael Bayer (@zzzeek) wrote: my point was, put the stack trace when you first post the issue, so that I can identify the problem without actually having to generate a complete test and run it. just saves me five minutes, that's all. |
Migrated issue, originally created by Dmytro Starosud (@dima-starosud)
This is using sqlalchemy 1.2.0b3.
Please considering following code snippet. It fails with an error (shown in code). However there is a workaround to just add
table = None
tomy_literal
, but I suppose this may lead to other problems.Stack trace.
The text was updated successfully, but these errors were encountered: