> > Is the only solution to attach an instance (u.job = myjob) or is there
> > another solution that doesn't require me to build the instance?
> 
> if you want SQLA's delete-orphan capability, that's the only way.  If you 
> want to rely upon CASCADE rules in your DB to handle it instead, that's 
> another way to go.

thanks, and really... managing in the db is such a simple thing...

Is there a why to find out the related class (that one u.job should be
instance of) so that I can issue a query on that?


sandro
*:-)

--

You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.


Reply via email to