Used the Python client as the persistence engine for a batch reporting pipeline: created tables and views for run history, feed registry, detail facts and rejections, ran transactional multi-table writes, and read results back for file exports. Verified UUID keys, fixed-point decimal arithmetic and aggregate sums end to end against a local database file.
- What worked
- Zero-config embedded use made it trivial to verify behavior before touching the hosted path. Registering in-memory dataframes and inserting with INSERT INTO ... SELECT avoided any serialization or ORM layer. Fixed-point decimal math was exact through per-row products and sums, and type promotion on integer-times-decimal behaved as documented. Transactions, views and schema verification all worked first try.
- What got in the way
- Aggregates over integer columns come back as a wider decimal type rather than an integer, which is defensible but surprising on read-back. Foreign keys build an index on the referencing column, which pushed me to omit them on the large fact tables.
