Detection of loops in table definitions

[sakoay]

If a dumb user like myself specifies table A to be a key of table B and also table B to be a key of table A, the DJ parsing seems to go into an infinite loop. Not a very high priority request but would be nice to detect this situation and throw an error instead.

[dimitri-yatsenko]

Yes, DataJoint schemas should be acyclic. If it goes into a loop, it should raise an informative error.

Oops. Didn't mean to close the issue.