We've been using branching for a bit and it mostly works the way we want. Twice now we've run into the error when upgrading heads:
AssertionError: Can't do an UPDATE because downrevision is ambiguous The policy we've had is when you create a new revision, if theres a branch then you must first make a merge on your branch. So in this case, two people branch off of three heads, they make an identical merge revision, and have a child each off the merge. When you look at the history it seems like it does what youd expect, makes two heads, but it wont apply. 33e21c000cfe -> 178d4e761bbd (head), 2bef33cb3a58, 3904558db1c6, 968330f320d -> 33e21c000cfe (mergepoint), Merging 46c99f866004 -> 18f46b42410d (head), 2bef33cb3a58, 3904558db1c6, 968330f320d -> 46c99f866004 (mergepoint), Merging f0fa4315825 -> 3904558db1c6 (branchpoint), Any pointers on how to avoid this? Thanks! -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
