Thank You, Mike.
--
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
SQLAlchemy release 1.1.14 is now available.
This release includes a variety of fixes for the ORM. Two of the
issues are critical stability issues involving garbage-collection
related bugs that are more likely to be seen within the Pypy
interpreter however are not necessarily limited to this
SQLAlchemy release 1.1.14 is now available.
This release includes a variety of fixes for the ORM. Two of the
issues are critical stability issues involving garbage-collection
related bugs that are more likely to be seen within the Pypy
interpreter however are not necessarily limited to this
On Tue, Sep 5, 2017 at 10:28 AM, Tony Locke wrote:
>
>
> On Friday, 1 September 2017 17:40:23 UTC+1, Mike Bayer wrote:
>>
>> On Fri, Sep 1, 2017 at 12:09 PM, Tony Locke wrote:
>> > No I don't think it's a bug because pg8000 is designed to always create
On Friday, 1 September 2017 17:40:23 UTC+1, Mike Bayer wrote:
>
> On Fri, Sep 1, 2017 at 12:09 PM, Tony Locke > wrote:
> > No I don't think it's a bug because pg8000 is designed to always create
> a
> > prepared statement if one doesn't already exists, and so that
>
> > Hence my question: what would
> > happen if I try to use blocking Sqlalchemy ORM in an asyncio app? I
> mean, I
> > need async because of slow endpoints, for example doing HTTP requests to
> 3rd
> > parties.
>
> Yeah I would offload that work into a queue and separate the CRUD part
>
There's no large numbers involved in any of the relationships, and
shouldn't be any conditionality. For the route I've been looking at as an
example, it is specifying a specific instance of Thing. My pre-route stuff
in Flask is loading a single instance each of what might be called