Can a Query Class update multiple tables at once ?
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 code.
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.
I love triggers.
On 16/3/18 9:31 am, Clifford Ilkay wrote:
> On Wed, Mar 14, 2018 at 8:18 AM, Mike Matthews <firstname.lastname@example.org> wrote:
>> Hello Doug,
>> I have always thought of Triggers like this. They sit outside of Omnis
>> and are absolute, but may need writing for each SQL backend though. They
>> need some understanding of course, but they also off load processing time
>> to the DB, which helps performance to the the user.
> It’s not just a performance thing. On the project I’ve been working on, one
> of the requirements for HIPAA compliance was to have an audit log of
> various user actions to determine who did what and when. We have two
> applications going against the same SQL Server database, Omnis Studio
> 22.214.171.124 and our Node.js application server. We didn’t want to write code in
> two different places to deal with this so we created stored procedures that
> are run via triggers that writes to an independent audit log database. Even
> if we were 100% Omnis or 100% Node.js, I’d still opt for the same solution
> because it’s simple, secure, and effective.
> Clifford Ilkay
> +1 647-778-8696
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:email@example.com