[PLUG] db auditing and LINQ

[Tim Bruce]

Ted,

That was probably me....

I can't speak specifically for that topic inside databases in general, but
I seem to recall something about that in some of my reading about MySQL.
Using the API (in MySQL, I'll stay away from other engines) cuts down on
some of the overhead and allows for faster performance (from my limited
reading of the API on MySQL).  I'd love to explore that and confirm it but
I don't have any experience programming any of the database engines using
APIs (my function is as a Production Support DBA rather than a Development
DBA).

That said, from my understanding it makes sense that the Triggers may not
"fire" if updates are made using non-SQL structures.

As a side note, based on our conversations at the Lab, were specifically
that some auditing may not be captured using LINQ and that Views are used
to lock down data to ensure sensitive (or restricted) data is not viewed
directly in a table.  Stored Procedures (and Triggers) can enforce logic
and updates local to the server (reducing network traffic if large table
scans (ugghh) are required or multiple and/or complex look-ups or parallel
updates are required).

If I am the person you were thinking of, we can take this off list and you
can email me directly.

Tim
-- 
Timothy J. Bruce

visit my Website at: http://www.tbruce.com
Registered Linux User #325725

-- 
Timothy J. Bruce

visit my Website at: http://www.tbruce.com
or visit my Space at http://www.MySpace.com/kb0odu
Registered Linux User #325725

On Tue, February 12, 2008 12:24, Ted Kubaska said:
> Last week at the Lab I was talking with someone about db auditing and
> LINQ.
> There's some discussion going on at the padnug yahoo group about LINQ and
> db
> auditing.
>
> Whoever I was talking to at the Lab said that db auditing and LINQ did not
> work together, but I don't have enough experience to comment on that. But
> I'd like to participate in that discussion and there's one beginning on
> the
> padnug site. Here's a comment that I "sort-of" understand but would like
> to
> understand better.
>
> <start quote>
>
> MySQL triggers are activated by SQL statements only. They are not
> activated by changes in tables made by APIs that do not transmit SQL
> statements to the MySQL Server; in particular, they are not activated
> by updates made using the NDB API.
>
> <end quote>
>
>  -ted
>
>
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>