I think what you actually would need to do is implement your own version of the DBAPI (effectively a parodying DBAPI). Then you would just configure a SQLAlchemy engine to use that DBAPI.
In this scenario, a requests session would be started on the acquisition of a cursor (or maybe on connect()). Execute could lazily set the query up and fetch would execute the SOAP request, download all rows (unless the SOAP service supports pagination) and cache them locally. Brian > On Apr 3, 2016, at 1:27 PM, Nathan Nelson <nrnel...@gmail.com> wrote: > > hood. -- 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 post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
