On Wednesday, April 27, 2016 at 6:41:24 PM UTC+2, Mike Bayer wrote: > > > > On 04/27/2016 11:11 AM, Mike Bayer wrote: > > > > I'm improving our test suite by ensuring that result processors are > > fired off for all result proxy subtypes when caching is used as well and > > I will ensure the line of code you mention is exercised. If I can > > reproduce your described issue at that level, then the bug will be > > located and fixed. I'll keep you posted. > > > > with query caching enabled the issue is reproduced with new test cases, > a fix for the issue is in review via the link at > > https://bitbucket.org/zzzeek/sqlalchemy/issues/3699/buffferedcolumnresultproxy-with. > > >
I would like to thank you Mike very much for your assistance, perseverance, invaluable help and the fix. Your support is exemplar. Best regards from users of your excellent SQLAlchemy, Marcin Raczyński i Piotr Dobrogost from Poland ps. The original investigation of the issue and suggested fix was done by Marcin Raczyński. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
