-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sqlalchemy MonetDb dialet question #49
Comments
I temporarily changed the code to: ` def has_table(self, connection, table_name, schema=None):
|
Did you clone the repo or did you install it from Pypi? this should be fixed in the newer versions. These aren't on Pypi however. |
Hi @MitchellWeg , got a question here. I've just encountered the same problem when I tried running This is the current implementation:
but this code executes correctly:
So it looks like bindparams need to be moved from a keyword to a method. So the question is - is the project still being maintained and can do a PR for this? Latest version was from 2017 and there's mention that this is fixed but it's definitely not fixed on pypi and it looks like it's not fixed here either. |
We currently have different priorities, but we try to maintain the project. PR's are always welcome! |
also work on the sql alchemy 2.0 driver/dialect is underway. |
@MitchellWeg I'd like to fix this, as the solution is already ready, but I seem to be having problems setting up the dev environment. If I understand correctly, to set up the dev env I should do: Thanks. |
Alternatively, in the meantime. For anyone encountering the same error. A workaround is something like this:
|
I got following error: TypeError("text() got an unexpected keyword argument 'bindparams'"). I found that: dialet .py "has_table" method is using sql.text(...., bindparams...). I changed the SQL text to be static without parameter marking to get it working. I'm new to MonetDb. Is this related to my SqlAchemy version (1.4) or some incompatible driver?
pip3 list
SQLAlchemy 1.4.23
sqlalchemy-monetdb 1.0.0
pymonetdb 1.5.1
The text was updated successfully, but these errors were encountered: