The fix mentioned in the ticket works for me.
Thanks,
Dheeraj
On Friday, 28 June 2013 20:45:50 UTC+5:30, Michael Bayer wrote:
>
>
> On Jun 28, 2013, at 10:26 AM, RedBaron >
> wrote:
>
> Thanks for the reply. I understand that update against multiple tables is
> non-standard. However, I think I
On Jun 28, 2013, at 10:26 AM, RedBaron wrote:
> Thanks for the reply. I understand that update against multiple tables is
> non-standard. However, I think I am trying to update only one table (events).
> The equivalent of what I am trying to do is
> update event set is_deleted=1 where (sid,cid)
Thanks for the reply. I understand that update against multiple tables is
non-standard. However, I think I am trying to update only one table
(events).
The equivalent of what I am trying to do is
update event set is_deleted=1 where (sid,cid) in (select
event.sid,event.cid from event join iphdr o
On Jun 28, 2013, at 10:14 AM, Michael Bayer wrote:
>
> I've created http://www.sqlalchemy.org/trac/ticket/2768 for this, and to
> understand what's going wrong one needs to appreciate that UPDATE.. against
> multiple tables is a non-standard syntax, where different backends put the
> second
On Jun 28, 2013, at 8:23 AM, RedBaron wrote:
> But when I try to write it in SQLALchemy
>
> inner_q =
> session.queryEvent.sid.label('sid'),Event.cid.label('cid')).options(lazyload('*')).join(Event.iphdr).filter(IpHdr.ip_dst==func.inet_aton("192.168.2.10")).subquery()
> update_stmt =
> tEvent
Hi,
I am using SQLAlchemy - 0.8.1
Background - I have a table "event" which has a flag 'is_deleted'. This
table has a composite primary key (sid,cid). There are many other tables
related to "event" that store information regarding that event - e.g.
"iphdr". I want to give the user an option of
