3 ms·
We do this too. Also allows for making changes purely at SQL level without having to do code changes - as long as the select clause signature is the same, the a
by noisy_boy 2y ago
We do this too. Also allows for making changes purely at SQL level without having to do code changes - as long as the select clause signature is the same, the application doesn't know any better. The downside is that you have to be careful not to a build an impenetrable nesting of its-views-all-the-way-down.
Yet again, balance.
- jayknight 2y agoWe have an in-house migration management system that allows us to update views pretty safely and reliably, even with nested dependencies. Basically, on every release, all of the views are dropped and recreated, so we don't have to worry as much about that. (But still be very careful with nesting your views)