4 ms·
I might look at it for work. Compliance requires us to keep track of who made what change when, and who it was approved by in case regulators need it. Right no
by curryst 6y ago
I might look at it for work. Compliance requires us to keep track of who made what change when, and who it was approved by in case regulators need it.
Right now, this often means making an MR on Git with your snippet of SQL, getting it approved, and then manually executing it. This would let us bring the apply stage in, as well as avoid "that SQL query didn't do exactly what I expected" issues.
It's possible to do it within the SQL engine, but then I have to maintain that, which I would prefer not to do. As well as dealing with performance implications from that.
- zachmu 6y agoThat's a great use case, let us know how we can help. We have a discord if you want to chat about it: https://discord.com/invite/RFwfYpu https://discord.com/invite/RFwfYpu
- martincolorado 6y agoI see a use-case for public resource data sets. For example, right of way, land use variance, permits, and land records. These are fundamentally public data sets that are often maintained by entities with limit budgets and the potential (even incentive) for fraud is substantial. Also, there is significant value in being able to access the data set for analytical purposes such as real estate analysis.