If you are logging errors, then maybe you should look at using a file
instead of a database table. I have seen an instance where a system
used a table for error logging and writing to the log table caused and
error, you can guess where that left things.....
Shawn McKenzie wrote:
Mark Bomgardner wrote:
I am writing an application in which I want to create log files. I am
weighing the difference between using text files and using a database to
house the data. It appears to me that there is really no advantage
either
way or is there? There are pros and cons to both methods, but I am
concerned about opening and closing a text file some many times that
it may
cause and issue. The file may be opened and closed 1,000 or more times a
day.
Opinions please..
markb
Using a database you're hitting a file the same number of times (the
database is in a file or files) but you have the mem/cpu overhead of
the db itself. Having said that, if you are using a database already
for the site then might as well log to it. I wouldn't implement a
database only for the purpose of logging.
-Shawn
--
Option Systems Pty. Ltd.
53 Waverley Road, Malvern East, VIC 3145
PO Box 7, Caulfield East, VIC 3145
Phone: 03 9571 0100 Fax: 03 9571 0500
The information in this e-mail is confidential and is intended solely for the addressee.
Any views or opinions presented are solely those of the author
and do not necessarily represent those of Option Systems Pty.Ltd.
If you are not the intended recipient, please delete this message and
contact the sender.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
