+1 on seeing thoughts in response to Iain's post!
On Tuesday, May 1, 2012 8:14:42 AM UTC-7, Iain Duncan wrote:
Hey all, we've been using SQLAlchemy for about 5 years now, currently with
Pyramid, but have not ever deployed to anything other than a standard vps
for a one client install.
Hi everyone!
I'm currently working on a query that makes the (rather bad) MySQL
optimizer choke. After running EXPLAIN, I noticed that MySQL was taking a
pretty long time to optimize it (about 130 seconds) and was then producing
a rather unintuitive join order. I tried replacing the JOIN
I have a m2m relationship of Posts and Categories. A post can be in any
number of categories, and a category can have any number of posts. This
relation is defined on the Post model:
categories = relation(Category, lazy=True, secondary=PostCategory.__table__,
this question is arising with unusual frequency in recent weeks, which suggests
a shortcoming in the docs. Rather than answering here, I've added what is
hopefully a comprehensive answer to the documentation; it would be helpful if
you could confirm for me that it answers your question, or if
The documentation is fine, I just get lost in it sometimes because there is
so much, and I have a hard time tracking down the specific thing I'm
looking for.
It turns out I was just overcomplicating things. Once I removed 'cascade'
from the ref, everything works as expected. Had I just left
well dont worry, that doc is new as of an hour ago, and I dont think that
behavior is actually explained anywhere; historically, people tend to not worry
about it and it just happens, though there have been stackoverflow questions
about it lately. it's better that it's described.
On Jun 25,
I have a one-to-many relationship from parent to items. In my Parent class
I define the items relationship like so:
items = relationship('Item')
I am using a soft-delete mechanism on items and I'd like to be able to
filter this relationship so it only returns active items. It there a
