Using Respawn for databases with "complex" relationships about respawn

[jbogard]

Support for complex circular dependencies now in 3.0

[jbogard]

So what you're really referring to is circular references, right? In terms of "real world" we use it on all of our projects, some with in the hundreds of tables so I'm not sure what qualifies "real world" or not.

The example you have doesn't show a circular reference though. If you want to deal with circular references, you'll need to ignore those tables and use FK disabling to do so (disable FKs, truncate tables, enable FKs).

Although I've seen quite a few "real world" databases that have zero referential integrity, and Respawn won't work for them of course.

[thiagomajesk]

Hi @jbogard, thanks for the prompt reply...

So what you're really referring to is circular references, right?

Not only (but that's why I've linked Issue: #12). As you have already noticed, the example I provided can't be handled by Respawn, and It is not clear to me why.

In terms of "real world" we use it on all of our projects, some with in the hundreds of tables so I'm not sure what qualifies "real world" or not.

That's a really good indicator to me.
Would you suggest that this problem could indicate that my current schema modeling is problematic?

The example you have doesn't show a circular reference though. If you want to deal with circular references, you'll need to ignore those tables and use FK disabling to do so (disable FKs, truncate tables, enable FKs).

This seems a lot to ask from a test setup point of view, don't you think? Couldn't Respawn provide some built-in solution for those cases?

PS.: I think would be great to have documentation for some common use cases like this

[jbogard]

No I actually don’t know what’s wrong with your original example. It doesn’t show anything to me that Respawn can’t handle. And I suppose it could handle those situations, but for our projects we let Respawn handle just about everything and stuff it can’t we add another custom step.

…

On Fri, Jan 5, 2018 at 4:53 PM Thiago Majesk Goulart < ***@***.***> wrote: Hi @jbogard <https://github.com/jbogard>, thanks for the prompt reply... So what you're really referring to is circular references, right? Not only (but that's why I've linked Issue: #12 <#12>). As you have already noticed, the example I provided can't be handled by Respawn, and It is not clear to me why. In terms of "real world" we use it on all of our projects, some with in the hundreds of tables so I'm not sure what qualifies "real world" or not. That's a really good indicator to me. The example you have doesn't show a circular reference though. If you want to deal with circular references, you'll need to ignore those tables and use FK disabling to do so (disable FKs, truncate tables, enable FKs). This seems a lot to ask from a test setup point of view, don't you think? Couldn't Respawn provide some built-in solution for those cases? PS.: I think would be great to have documentation for some common use cases like this — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#32 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGYMtGOnJsDc2r-u1IjrL1mbnfvf4PMks5tHqf1gaJpZM4RUV9G> .