For what it's worth, I've never used SQLAlchemy's ORM capabilities and
don't support it in sAsync. I agree that it really isn't compatible with
the asynchronous nature of Twisted, and I don't see it as adding
anything. To me, the power of SQLAlchemy is in the clean and convenient
way it permits
Stephen Waterbury writes:
> This is a good point -- although the attractive part of using an
> ORM in the first place is somewhat OT here, the main attraction
> for me is usually *DRY* rather than "automatic persistence", so for
> my purposes such "magical" features as direct attribute access,
>
David Bolen wrote:
... or that any interaction that might require going back to the
database only be through wrapped methods and not direct attribute
access. This can turn out to be a bunch of extra work when you start
talking about walking lists of related (one to many) records,
traversing the
Don Dwiggins writes:
> So if someone wanted the use of the ORM, would you say that they
> should access the objects through deferreds, just as they would with
> SQL? Or is it worse than that?
If by deferreds you mean pushing the ORM operation (including all
possible ancillary object loading) in
Hi Colleagues:
I guess I am making today "Look at Twisted Documentation Day." I am looking at
ticket 1009.
For inline generator examples, here is the example I use in "Adventures in
Stackless Python Twisted Integration." In turn, this example comes from the
discussions in I believe January 20
Hello Colleagues:
>For ticket 1138 (cool movie), when I access the URL:
>http://twistedmatrix.com/projects/core/documentation/howto/tutorial/deferred_tutorial.html
>I get, URL not found. Which deferred tutorial are you referring to?
>>"Deferreds are Beautiful (A Tutorial) at :
>http://twistedmatr
David Bolen wrote:
It's much trickier if you want to use the ORM, unless you are very
careful to fully eager load every thing in any possible database
operation if you have need of the information subsequently in your
twisted code. Otherwise you may block unexpectedly simply when
accessing your
"Maciej Szumocki" writes:
> I'm using SQLAlchemy with Twisted in a large project without
> problems. Why would you think you cannot? You just need to run SA
> operations in non-reactor threads (i currently use my own threadpool
> and deferToThread but it's only slightly modified standard twiste
> From: Ryan Lepidi
> Subject: [Twisted-Python] So how does everyone use an ORM in twisted?
> To: twisted-python@twistedmatrix.com
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I have searched a bit, and it seems as though you can't use SQL Alchemy with
> twisted due
On Tue, 17 Mar 2009 11:05:59 -0400, Ryan Lepidi wrote:
I have searched a bit, and it seems as though you can't use SQL Alchemy with
twisted due to SA being thread unsafe. The only solution I found was sAsync,
but this is old and unmaintained. What is everyone else doing for database
access for a
I have searched a bit, and it seems as though you can't use SQL Alchemy with
twisted due to SA being thread unsafe. The only solution I found was sAsync,
but this is old and unmaintained. What is everyone else doing for database
access for a multiuser server? Is everyone really using raw sql querie
On Tue, 17 Mar 2009 15:18:31 +1100, Sury Soni wrote:
Hi,
I have an existing application, written using Ice Middleware
(www.zeroc.com)
This application is my source of infinite queue (server)
Following is my application (processing client to my infinite queue
server) idea to be implemented usi
12 matches
Mail list logo
