Sj wrote:
On Fri, 18 Mar 2005 09:24:01 +0100, Nicolas Weeger
<nicolas.weeger(a)laposte.net> wrote:
>>The part I don't like is that there is
no trace
>>
>>
It would be a nice optional feature to turn on database-auditing for
all changes to the database, which would provide a trace for such
things. But that doesn't exist yet. I agree that without such a
solution, it's most transparent to do such things as a logged-in user
(with sysop capacity, if neccessary) rather than as a developer. +sj+
Hoi,
Given the large amount of changes to our database, database-auditing
would be expensive in resources and it would be over and above the
current history that we maintain. This might be something that we do not
want as this may also impair the scalability of our application. :)
Thanks,
GerardM