× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Nathan, my thinking on using a journal for this is that would put all file
activity on the same place.


Okay, but wouldn't that be a disadvantage for you? Querying journals is
harder than databases.


Reads, updates and deletes.


My understanding is that only database changes are recorded when you start
journaling on database files - not reads. You'd still need a trigger to
"send" reads to journals, using a system API.


If the question that is being asked is who did anything to this file
having it all in one place makes sense.


Yes. But wouldn't it make more sense to record reads, inserts, updates, and
deletes in a database for query purposes?

Also in my specific case an end user would never be asked to query the read
log, that would only be taken by someone with security officer privileges.


I don't see how that might be relevant. Security officers have more skills;
more tools?


If the only question to be answered is who read a record and that end
users needed to get at the data then a database makes more sense. I was
also thinking that writing to a journal would be much faster than writing
to a database.


I haven't tested the performance. But my suspicion is that writing to a log
file would perform better than using an API to send record images to to
journal.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.