Replying to my own post: It appears that I've resolved this problem by removing the reciprocal relationship (backref) from this particular relation. Though it is a bit of a head-scratcher as to why the removal of the backref resolves the circular dependency problem given that this table has many other relationships defined to other lookup tables that are modeled identically and do not exhibit any circular dependency problems.
On Sep 24, 10:49 am, Randallabra <[EMAIL PROTECTED]> wrote: > There is a case in my application where setting the attribute > 'version' which is the name of a relationship to a look up table. When > I avoid setting this attribute, saving the record takes 0.15s, however > when I set the value of this relationship, saving the record takes > upwards of 30 seconds. > > Furthermore I am seeing a CircularDependencyError, but only when I set > the value of this attribute: > > sqlalchemy.exc.CircularDependencyError: Circular dependency detected > [(<sqlalchemy.orm.identity.IdentityManagedState object at 0x37ff070>, > <sqlalchemy.orm.identity.IdentityManagedState object at 0x1808110>), > (<sqlalchemy.orm.identity.IdentityManagedState object at 0x1808110>, > <sqlalchemy.orm.identity.IdentityManagedState object at 0x37ff070>)][] > > Is this error indicative of a problem with the relationship I've > defined? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
