On Wednesday, July 13, 2016 at 11:03:04 AM UTC-4, Niall wrote: > > If I'm understanding what you're both saying then the best approach may be > to abandon using my customized db wrapper and go back to using standard > sqlalchemy >
Not really. I'm suggesting that it may be *quickest* to use SqlAlchemy (or model a service after it) to handle the database connections. Between the zope.sqlalchemy package, pyramid_tm, and the sqlalchemy scaffold you will have a system that connects to oracle and wraps every request in a transaction, and does it all using a proven connection pool. You can then obtain an underlying connection from SqlAlchemy and then alter your existing code to use that connection, instead of connecting to oracle yourself. Please remember: you haven't shared any of your code for this "db wrapper" so we don't know what it's doing. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/8633fc87-3e08-4f7c-9fb9-1b416cba1edd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
