A part table that references a table downstream of its own master breaks delete, drop, trace and list_tables on the connection
Los mantenedores suelen responder en 6 días
@dimitri-yatsenko ya está trabajando en esto.
Desde el 17/10/2026.
- #1620 de @dimitri-yatsenko — abierto
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start with topo_sort() in dependencies.py, then inspect its callers in Diagram._propagate_restrictions, Diagram._propagate_restrictions_upstream, diagram iteration, and Schema.list_tables(), plus the Table.declare() and Part declaration paths. Run the provided reproduction to cover cycle detection, ownership classification, declaration validation, and unaffected operations. Done means owned-part cycles are rejected with the specified DataJointError, unowned parts are warned about and sorted independently, existing-cycle operations fail clearly, and unrelated operations continue working.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
DataJoint accepts a part table whose reference makes its master-part group depend on itself. After that declaration, every cascading delete, every drop, Diagram.trace() and Schema.list_tables() on the connection fail with networkx.exception.NetworkXUnfeasible. This includes operations on tables that have nothing to do with the cycle, and dropping the part that caused it.
Reproduction
import datajoint as dj
schema = dj.Schema("repro_group_cycle")
@schema
class Session(dj.Manual):
definition = """
session_id : int32
"""
@schema
class Analysis(dj.Manual):
definition = """
-> Session
analysis_id : int32
"""
@schema
class Subject(dj.Manual):
definition = """
subject_id : int32
"""
# Later, a part is added to Session that references Analysis.
class Session(dj.Manual):
definition = """
session_id : int32
"""
class Summary(dj.Part):
definition = """
-> master
-> Analysis
"""
schema(Session) # succeeds: session__summary is created
Each of these then raises networkx.exception.NetworkXUnfeasible: Graph contains a cycle or graph changed during iteration:
Session.delete()
Subject.delete() # Subject is unrelated to the cycle
dj.Diagram.trace(Analysis & {"session_id": 1})
schema.list_tables()
Session.Summary.drop(part_integrity="ignore") # so the part cannot be removed through DataJoint
Observed on MySQL and on PostgreSQL with the current master.
Cause
topo_sort in dependencies.py keeps each part right after its master. To make that possible, it orders a master after every table that its parts reference. Here Session.Summary references Analysis, so Session has to come after Analysis, while Analysis references Session and has to come after it. No such order exists, and nx.topological_sort raises.
In general: treat each master and its parts as one node. The tables can be ordered exactly when these groups do not depend on each other in a cycle. Besides the case above, two masters whose parts reference each other's masters also form a cycle: A.Part references B, and B.Part references A.
Diagram.cascade(), Diagram.trace(), Diagram iteration (used by delete and drop) and Schema.list_tables() each sort the whole dependency graph loaded on the connection. That is why a single cycle breaks them for every table.
topo_sort also decides group membership by the table name alone (master__part). A part that never references its master, or references it only through a secondary or nullable foreign key, is still pulled next to its master. That causes failures in both directions:
m;xreferencesm; partm__preferencesxbut notm. Nothing here is circular, yettopo_sortraises, because it ordersmafterx. Even without that, keepingm__pnext tomwould place it beforex, which it references.m; partm__p1referencesmonly through a nullable foreign key; partm__p2referencesmin its primary key and also referencesm__p1.topo_sorttreatsm__p1as part ofm's group and sorts this. Butm__p1is not tied to a master row: it is a table that depends onm, andm__p2depends on it.
Expected behavior
- A part belongs to its master's group only when it is owned by the master: a foreign key in the part's primary key references the master, or references another owned part of the same master. The reference may rename the key attributes. Any other part is treated as a separate table when DataJoint orders tables.
- Declaring an owned part whose reference would close a cycle raises a
DataJointErrorbefore any table is created. The message names the part, the referenced table and the cycle. An owned part may still reference its master, another owned part of the same master, or any table that does not depend on its master. - A cycle that already exists in a database (declared before the check) raises a
DataJointErrorthat names the cycle instead of a networkx error. Only the operations that must order the cycle raise it. Operations on other tables, and dropping the part that closes the cycle, keep working. - A part that is not owned gets a warning at declaration. It is sorted as a separate table, and delete and trace are expected to treat it the same way in 2.4.
Where
Table.declare()calls the_declare_check()hook after parsing the definition and before running any DDL.Partcan override it.topo_sort()independencies.py, and its callers:Diagram._propagate_restrictions,Diagram._propagate_restrictions_upstream,Diagram.__iter__/__reversed__, andSchema.list_tables().
- Lenguaje dominante
- Python
- Estrellas
- 198
- Forks
- 103
- Merge medio
- 6 d 1 h
- PR fusionados (30 d)
- 10
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de datajoint/datajoint-python
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1703 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1702 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
datajoint/datajoint-python#1701 ·
Los mantenedores suelen responder en 6 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
datajoint/datajoint-python#1691 ·
Los mantenedores suelen responder en 6 días
-
dependencies needs-discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
datajoint/datajoint-python#1687 ·
Los mantenedores suelen responder en 6 días
Todos los issues de datajoint/datajoint-python
Issues similares
-
needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
gke-labs/kube-agents#6620 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#34719 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
cognition
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
One non-object JSON record makes the session catalog exitPosiblemente ocupada @he-yufeng la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
[Suggestion]: Geonode MCP ServerAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
collabnix/awesome-mcp-lists#433 ·
Los mantenedores suelen responder en 4 días