Hi Mike. First, txs for your awesome package. This WAS NOT meant as a dump on SQLAlchemy to fix and you're in fact victim of your own success - I'm by now too lazy to connect directly to databases, but rely on SQLAlchemy to mediate even if I skip the ORM features and use raw sql. I suspect the core issue is somehow related to pytest, since both SQLAlchemy and cx-Oracle behave as expected without it.
This is more of a heads up "this can happen and this is what I did". No one's being asked to fix anything - hard enough to do when 2 vendors are involved, worse when 3 are. My code knows very little about cx-Oracle, because it doesn't have to. The weird behavior is mediated via SQLAlchemy, even if it may not be the cause. But I suspect pytest would say "not me" and cx-Oracle would do the same. Far as I understand cx-Oracle is set up correctly and pytest should not care what db libraries are up to. As the one variable in works/doesnt work, pytest stands out but no one there is likely to really care about db packages. As the "code I talk to" I chose this forum to post some feedback on what happened to save future users some grief. I'll try to see if I can replicate the behavior by cutting out SQLA and doing cxOra with/without pytest. Meanwhile, this is strictly a FYI, NOT a request to fix and should not be taken as a critique of SQLAlchemy. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/CAJdYTXGYaU2GcPP3FSgOMXQ7Bgb1NMK%2B0Qu7fFMmhfVLG0UyNw%40mail.gmail.com.
