Open jasheldo opened 3 years ago
Can confirm I have the same issue. Temporary fix is to force SQLAlchemy==1.3.23 until this is resolved.
I don't think this library is maintained anymore and the one that supersedes it is not open source or at least not developed in public afaict. I'm not going to bother trying to get anything out of teradata official support, but if you edit the dialect.py file in the installed location and remove the inline argument completely and change it to column_keys=column_keys
in the super call, it will work again.
Thanks. Indeed it looks like the new pypi package for teradatasqlalchemy may have fixed this in version 17.0.0.2 I had to manually look through the package after downloading it to verify. How unfortunate they've removed the development from public view
I had the exact same issue. However, upon debugging, I noticed that my error was in the compiler.py file and not dialect.py file. Nevertheless, @jseabold 's solution worked perfectly. I opened the compiler.py file in the sqlalchemy site package, removed the inline argument completely and changed it to column_keys=column_keys
in the super call.
Same here. There were a couple issues I noticed in my case:
Same here. After fixing the sqlalchemy to 1.3.23, everything runs normal.
sqlalchemy to 1.3.23 worked for me. Thanks a lot Maroon1989
After upgrading to
sqlalchemy.__version__>=1.4.0
, I've been receiving the title error.Prior to version 1.4.0, the following would work as expected.
I'm now met with the following StackTrace:
Here's my full environment for reference. Per @zzzeek, this is a Teradata issue.
The issue I opened and close this AM, along with @zzzeek's suggested fix is here.