Thank you. Glad it worked out easily.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email
Hello,
* Apologies if this is a duplicate -- I attempted to post a few hours
earlier but the result vanished. Could be that the earlier effort went off
as a direct email to MB, instead of a post to this group as intended.
chris e posted about this topic in April and I was trying to respond on
p.s.: I'm curious whether this is the same issue mentioned in ticket
370, though that was apparently specific to Firebird's treatement of
rowcounts; here I'm on postgresql 8.2.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
On Jun 20, 2007, at 2:52 AM, Eric Ongerth wrote:
If I had to guess, maybe this 3-way split of secondary/association
tables is the thing that might be causing problems. I set it up
that way to keep a strong, up-front distinction between events
being in an item's future vs. its
Thanks. I'll be getting back to this tomorrow too. Meanwhile: please
note -- easily overlooked, item.current has uselist=False in its
relation to Gearset because an item can only *currently* be involved
in, at most, one set of items / one in progress reservation.
However, item.history and
ok its fixed in 2750 and it was mega-dumb, yes it was the
uselist=False. lets pretend this one didnt happen this late in the
game
On Jun 20, 2007, at 2:52 AM, Eric Ongerth wrote:
items = Table('items', metadata,
Column('id', Integer, primary_key=True, autoincrement=True),
send me a reproducing test case, or at least let me see your
mappings. in particular, dont mix a mapping on a table that is also
used as secondary in a many-to-many relationship.
On Apr 17, 2007, at 5:47 PM, chris e wrote:
I'm not sure why. But when I do a delete/sql alchemy seems to be
