-
Notifications
You must be signed in to change notification settings - Fork 30
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
OneAgent SDK causing breaking changes with DB cursors #76
Comments
I am having a hard time reproducing, would you mind sharing a piece of code that allows you to access the rows like that? When I run cur = conn.cursor()
cur.execute("SELECT tablename, tableowner FROM pg_catalog.pg_tables")
for row in cur:
print(row['tablename']) I get the same error as you, even without autodynatrace installed |
Are you per chance using cursor_factory=RealDictCursor # or DictCursor In the connection creation? I think I was able to reproduce by using that, and will look to implement a fix |
@dlopes7 you are correct! we are using |
Hi @dlopes7! There might be a minor misspelling in this update: extras vs |
@dlopes7 - Hi - just checking to see if you saw Casey's last comment. Are you able to reopen this and/or create a new issue to address the misspelling that he mentioned? |
Hi! We are trying to incorporate the OneAgent SDK into our codebase.
Currently on
oneagent-sdk~=1.5.0.20221221.150433
,psycopg2==2.9.5
running on Python 3.7.2.Our
create_app()
flask function essentially runs this:After incorporating the SDK, all of our DAO objects/queries are behaving differently.
We can no longer pull a field value by name out of a DB cursor:
We'd really appreciate any suggestions on tackling the issue. Please let me know if I can further clarify anything here. Thanks!
The text was updated successfully, but these errors were encountered: