11 ms·
I agree with that being fastest, but not cheapest. In my experience these one off reports are very brittle. The app ends up making schema changes that are brea
by ElatedOwl 1y ago
I agree with that being fastest, but not cheapest.
In my experience these one off reports are very brittle. The app ends up making schema changes that are breaking to these one off reports, and you usually don’t find out until it goes to production.
I’ve dealt with the maintenance nightmare before. At current gig we’re exploring solutions, curious what a robust pipeline looks like in 2025.
The ORM piece is interesting — we use ActiveRecord and Ruby, and accidentally breaking schema changes within app will get caught by the unit test suite. I would love for a way to bring OLAP reports in similarly to test at CI time.
- wredcoll 1y agoI mean, if you're relying on tests to catch schema changes... then test your sql reports? This doesn't seem like an amzingly cool solution but if that's the one you're already using...
- lpapez 1y agoWhy not test the OLAP reports? Surely there is a way to run a raw query in Rails/ActiveRecord and use it in a smoke test?
- datadrivenangel 1y agoThey call this Data Contracts.