hello michael, friends,
here is my test case.
thanks a lot for your consideraion. please take a look.
from sqlalchemy import create_engine
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy import Column, Integer, String, Unicode, ForeignKeyConstraint
from sqlalchemy.orm
thanks - though one thought I had is, why not just modify an existing
ForeignKeyConstraint.onupdate directly in the event, instead of trying to add
the constraint later and confusing the ORM. you wouldn't need the relationship
arguments then.
the constraints for the table are in
oh also your foreign_keys is wrong. PageData has a foreign key to Lang. So
foreign_keys=[lang_code], lose the uselist which is never necessary except
for one-to-one.
On Jul 16, 2012, at 5:18 AM, alex bodnaru wrote:
hello michael, friends,
here is my test case.
thanks a lot for your
thank you very much michael.
both ways worked like a charm.
i have implemented the other way, though this is better and more general: any
constraint with onupdate or ondelete attributes should have these attributes set
to none if the dialect name is mssql.
thanks a lot,
alex
On 07/16/2012
W
TIM: la tua mail in mobilità con il BlackBerry®
-Original Message-
From: alex bodnaru alexbodn.gro...@gmail.com
Sender: sqlalchemy@googlegroups.com
Date: Mon, 16 Jul 2012 18:51:28
To: sqlalchemy@googlegroups.com
Reply-To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] dialect
TIM: la tua mail in mobilità con il BlackBerry®
--
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 to
