On 9/20/05, Michel Deloux <[EMAIL PROTECTED]> wrote:
> Hi all
>
> what's the best choice to store users actions in a CF
> application(inserts, updates and deletes)? DB or Log4J could be
> resolve this? Anyone use log4j? Any approaches?
>
> Cheers
I'm really late to this conversation, but for what
Hello MD,
if you want to log what's happening in the db (inserts, updates, etc) then log
that in the db itself, using triggers or, even better, check if your db has a
built in logging feature that can fulfill your needs. This means you don't need
to worry about it in cf, and it will even log mo
We have an app where we log every user action, it would get to about a
million rows in one week, so we log to csv file, and then have a daily
schedule which compiles all the raw data into totals - which comes to about
15 rows per day, and a lot less data. Then the reporting app can quickly and
easi
Thanks all. Using Michael example could be more robust because I can
store what I want. Using trigger this is more hard to do, right?
Michael do you can share that example using asinc gateway with us?
Thanks all
MD
2005/9/20, Michael Dinowitz <[EMAIL PROTECTED]>:
> I use an async process to log
While that doesn't explicitly delay user requests, it does contribute
to load on the server (both CF and DB), so it will have some effect on
overall system performance. I suspect that synchronous log4j calls
would still be faster to the user, as well as greatly reducing the
logging overhead, but a
I use an async process to log user information into a DB. Fast, effective and
has 0 impact on a user session while still having the logs the way I want them
(id for user agent, etc.)
The only limitation is that you need an async process (enterprise), use a hack
to CFMX 7
(http://www.fusionautho
,
and relatively easy data extraction with no performance impact.
-Dov
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 20, 2005 12:24 PM
To: CF-Talk
Subject: Re: Logging users actions - DB or Log4J?
If you want to log query actions, then a trigg
Barney is definately right about the db is going to be more resource
intensive than writing to a file. To me it would come down to how
much data you are going to be logging and for how long. Basically,
are you going to just be glancing at a log file every once in a while
and scrolling through it,
If you want to log query actions, then a trigger is the best, since
it'll be pretty much error proof if set up properly. If you want to
log business operations, then the DB/log4j distinction becomes a
matter of how you want to use the data. Obviously having the log data
in a DB facilitates easy r
On Tuesday 20 September 2005 16:58, Michel Deloux wrote:
> what's the best choice to store users actions in a CF
> application(inserts, updates and deletes)? DB or Log4J could be
If it's for the purposes of auditing what is going on, a DB is a much better
choice - esp. if the DB supports triggers
10 matches
Mail list logo
