astrodbtoolkit / astrodbtoolkit/AstrodbKit
Empty JSON array ([]) as a lookup-table reference file causes a confusing IntegrityError in load_table()
- Lenguaje dominante
- Python
- Estrellas
- 12
- Forks
- 5
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Where:** `astrodbkit.astrodb.Database.load_table()` does `conn.execute(self.metadata.tables[table].insert().values(data))` where `data` comes straight from `json.load()`. If the JSON file's top-level array is empty (`[]`), SQLAlchemy's `insert().values([])` is interpreted as "insert one row using column defaults" (a known SQLAlchemy quirk: an empty list to a multi-row `.values()` isn't a no-op), not "insert nothing."
**What happened:** After emptying `Publications.json`, `SourceTypeList.json`, and `ParameterList.json` to `[]` (clearing stale template-example placeholder rows before real data existed), `build_db_from_json()` failed with `sqlite3.IntegrityError: NOT NULL constraint failed: Publications.reference` — a single default-valued row was attempted, which violated the non-nullable `reference` column. The error message gives no hint that the root cause was an empty-array JSON file rather than a real data problem.
**Workaround:** Deleted the three now-empty JSON files entirely instead of leaving them as `[]` — `load_table()`'s existing `if os.path.exists(filename):` guard cleanly skips a missing file (with an optional verbose "not found" message), which is the actual correct way to represent "no data yet" for a reference table.
**Suggested change:** `Database.load_table()` should special-case `if not data: return` before calling `insert().values(data)`, so an empty-array reference file is a documented no-op instead of an inserted row of column defaults that then trips downstream NOT NULL constraints.
**Cross-filed:** Also filed against the [astrodb-bot](https://github.com/astrodbtoolkit/astrodb-bot) skills repo as [astrodbtoolkit/astrodb-bot#99](https://github.com/astrodbtoolkit/astrodb-bot/issues/99), which documents the same gotcha from the skill-user workaround side; this issue is for the actual `astrodbkit` fix.
---
_Reported from a gotchas.md log filed by a skill user (2026-08-28)._
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Start in astrodbkit.astrodb.Database.load_table(), where data from json.load() is passed to insert().values(data). Reproduce the behavior with a top-level [] reference-table file and follow build_db_from_json(); done means the empty file is treated as a no-op and no default-valued row or IntegrityError is produced.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python, sqlalchemy
- Área
- databases
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Activo
- Claridad
- Bien especificado
- Aptitud para principiantes
- 84/100