the error you're getting suggests an unusually long chain of dependencies between individual rows. There is a recursive element to the way that a flush plan is executed, but it generally is a shallow recursion. Your stack trace isn't making it clear where the bulk of the recursion is occurring.
Since the concepts you're representing don't seem like they should be like this, this is why we need to see the exact mapping that produces this error. On Jun 18, 3:37 pm, Marin <[EMAIL PROTECTED]> wrote: > > cant really tell unless you provide a fully functional, as simple as > > possible test case, preferably against sqlite, which can be run with > > no dependencies. > > I'll try to make one. I tried to fix it doday and got that the next > code does not produce the error: > test = Test() > section = Section() > section.Test=test > db_session.save(test) > for i in range(60): > q=Question() > q.Section=section > for j in range(6) > a = Answer() > a.Question = q > > db_session.commit() > > Is there a max limit on the number of SQL commands that SA can isue > between a BEGIN-COMMIT? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
