ZdenekSrotyr 2d6a94fb6f fix: DuckDB concurrency — WAL mode, subprocess sync, temp+rename ... Three-pronged fix for DuckDB lock conflicts: 1. WAL mode on system.duckdb — enables concurrent readers + writer 2. Sync trigger runs extractor as subprocess (not background task) — separate process = separate DuckDB connections, no lock conflict 3. Both extractor and orchestrator write to .tmp then atomic rename — avoids lock conflict with API reads on extract.duckdb/analytics.duckdb Fixes #9 permanently.		2026-03-31 13:19:57 +02:00
..
tests	refactor: delete old sync pipeline — 9,500 lines removed	2026-03-31 07:50:37 +02:00
__init__.py	Extract Keboola into connectors/keboola module	2026-03-09 12:22:16 +01:00
client.py	fix: keboola client metadata_cache_path uses DATA_DIR instead of deleted config	2026-03-31 11:57:57 +02:00
extractor.py	fix: DuckDB concurrency — WAL mode, subprocess sync, temp+rename	2026-03-31 13:19:57 +02:00