review · segments
Map DAP orders table schema and cross-database connections
claude 58 events 1 segments dap-fos-enrichment
segment 1 of 1
Map the DAP orders table schema and cross-database connections
The assistant gathered information about the orders table by reading all migration files, the Order model, database config, .env.example, and searching for FOS/WooCommerce/Labworks integration points. It compiled a comprehensive report covering all 44 columns of the orders table, the Order model's casts and relationships, database connections (mysql, fos, labworks, sqlite), and existing integration files (FosMysqlCheck, LabworksCheck, PollLabworksOrders, SyncShippedAt).
outcome
Complete schema map of the DAP orders table with 44 columns, Order model details, 4 database connections, and 4 integration files documented.
next steps
—
key decisions
- woo_order_id was renamed to woo_id (unsignedBigInt) to match TDR app conventions
- uploaded_at, shipped_at, and financial fields were added as part of the Labworks replacement initiative
- fos_imported_at and photos_cached_at do not exist in the codebase yet
open questions
- What is the exact FOS database schema that the DAP needs to read from?
- What is the WooCommerce database schema that the DAP needs to read from?
- How should the FOS order import process work (polling, webhook, or batch)?
2 weeks ago → 2 weeks ago