I don't have the Eagle book, so I didn't steal it from there. Furthermore, if you notice, my tutorial has a SEE ALSO section. That references two other articles one can look at for more information on logging to a database using DBI. When writing my tutorial I had already read through the articles mentioned in the SEE ALSO section. That's why I mentioned them in that section.
Even had I not read through those articles, I venture to guess that I would have come up with pretty much the same table structure. And the reason why? Because those are the fields stored in the httpd access log, so presumably one would want the same information stored in the database.
Anyway, thanks for the "good tutorial" bit, I'm glad you liked it.
This is a neat article!!! You could really make things easier by writing a script to print all the info to the screen!!! Much easier that sorting through a .log file. You could even sort them by date and what not, so you only get that days, or even that time's specific error. Awesome!
Hmmm, I've been logging using a similar approach (REAL similar, in fact. I think by default, you'd end up with the same table structure regardless of who put it together).
But now the REAL question (and one I can't find ANY answer to: What magic SQL does one use to get anything worthwhile OUT of this data? Is there an SQLmonks.org that could help? Or is anybody interested in setting up a repository for useful open-sourced SQL code to handle log files? (i.e., glean the number of visitors? Number of visits? number of nonblack nonravens?)
I've got a few queries I've hacked together, but nothing compared to the visions of loveliness I had in mind when I started logging this info a few months ago.