Preventing Temporary Table Race Conditions and Namespace Pollution in Concurrent Batch Architectures

Описание и применение

В статье описывается подход к проверке гонок и загрязнения пространства имён при работе параллельных задач с временными таблицами в SQLite. Используется динамическое именование таблиц и изолированные пространства имён, что устраняет коллизии, в отличие от анти‑паттерна с фиксированным именем.

Задача

Concurrent batch workers using hardcoded temporary table names cause race conditions, namespace collisions, and data corruption.

Результат

The verification harness demonstrates that dynamic naming with isolated namespaces prevents race conditions and namespace pollution, whereas the anti‑pattern leads to deterministic failures.

Рабочий процесс

• Define a BatchTaskConfig schema with task_id, use_dynamic_naming, and payload_data.
• Implement run_batch_simulation to create a temporary table name based on task_id when use_dynamic_naming is true.
• Spawn multiple threads, each executing run_batch_simulation against a shared or private SQLite URI.
• Collect SimulationResult objects recording thread_name, table_name, success flag, error_message, and execution_time_sec.
• Aggregate results into a VerificationReport and serialize with orjson.
• Run the harness in a CI/CD pipeline to detect conflicts.

Доказательства

When executing the benchmark harness, the script terminated instantaneously with a ModuleNotFoundError: No module named 'orjson'

Источник

Forced unconditional import of orjson was declared at the top‑level module scope without guards.

Источник

The script had a brittle hard dependency on non‑standard packages.

Источник