Can a Query Class update multiple tables at once ?
On Thu, Mar 15, 2018 at 7:57 PM, Bastiaan Olij <firstname.lastname@example.org>
> Hey Clifford,
> Also keep in mind that logging changes isn’t just about what you’re
> users do when they are nicely logged in through your client app.
> It’s also about that forgetful developer that need to make that quick
> enhancements to your app and forgets he also needs to call the logging
> It’s also about logging what any hacker that somehow managed to get
> around your carefully crafted logic to make changes directly on a table.
> The trigger ensures that any change on your table gets logged, no
> questions asked, no way around it, thanks for coming, there you go.
Sure. That was another motivation for us to use triggers and stored
procedures. I can still think of ways that this can be subverted easily
enough. The DBA still has admin privileges on the entire database so with
some effort, they could alter the medical records and the audit log if they
were so inclined. With blockchain technology, that would not be so easy
because that data would be distributed in a globally distributed replicated
database with an unknowable number of nodes and each transaction would be
cryptographically signed and linked to the previous one.