Hi all;
Sorry if I'm asking a silly question - I'm very inexperienced with
databases. I'm playing around with using DBI / SQLite as a back-end for
parsing and storing log files - I have multiple columns like log date,
logged by, etc. I parse these in a Perl script, and then store them in
the
On Thu, Mar 29, 2007 at 07:53:55AM -0500, Nurmi, Michael V wrote:
Below is the output I get when I try to do a make on the DBI module in
Solaris 10. This works fine on Solaris I was wondering if I need an
updated module for solaris10? Is there any DBI module that works with
solaris10?
On Thu, Mar 29, 2007 at 11:40:02PM -0700, Philip M. Gollucci wrote:
Tim Bunce wrote:
file: $CPAN/authors/id/T/TI/TIMB/Apache-Status-DBI-v1.0.0.tar.gz
size: 4562 bytes
md5: 15e92e4c765793ae850191f9b02e8d83
Hi Tim,
I don't seem to have commit access to this repo yet.
no rush, I'm on
Hi George,
George Bills wrote:
Sorry if I'm asking a silly question - I'm very inexperienced with
databases. I'm playing around with using DBI / SQLite as a back-end
for parsing and storing log files - I have multiple columns like log
date, logged by, etc. I parse these in a Perl script, and
On 3/30/07, Tim Bunce [EMAIL PROTECTED] wrote:
On Thu, Mar 29, 2007 at 07:53:55AM -0500, Nurmi, Michael V wrote:
Below is the output I get when I try to do a make on the DBI module in
Solaris 10. This works fine on Solaris I was wondering if I need an
updated module for solaris10? Is there
Garrett, Philip (MAN-Corporate) wrote:
George Bills wrote:
I've also seen MySQL syntax like ON DUPLICATE KEY
UPDATE ... which looks good, but I'd like to avoid an extra
dependency on a database that has to be set up and maintained (hence
SQLite).
My preference for a solution would
On Fri, Mar 30, 2007 at 09:55:23AM -0400, Ronald Kimball wrote:
Garrett, Philip (MAN-Corporate) wrote:
George Bills wrote:
I've also seen MySQL syntax like ON DUPLICATE KEY
UPDATE ... which looks good, but I'd like to avoid an extra
dependency on a database that has to be set up and
I don't know if that would be speedy. Updates are far more expensive
than an insert. It does sound portable and safe though.
-Original Message-
From: Tim Bunce [mailto:[EMAIL PROTECTED]
Sent: Friday, March 30, 2007 9:47 AM
To: Ronald Kimball
Cc: George Bills; dbi-users@perl.org
On Fri, Mar 30, 2007 at 09:56:02AM -0600, Ian Harisay wrote:
I don't know if that would be speedy. Updates are far more expensive
than an insert.
That very debatable, but the point is that updates would generally be
more frequent than inserts in a typical increment counter scenario.
Tim.
It
I thought you said you are on perl 5.8 not perl 5.6? Looks like Solaris
64 bit (and not on Windows). Either way, DBI is failing so there is no
chance DBD::Oracle will work until you fix that. Fix that first :
If you have more than one perl in your path try calling the one that
does have DBI
From what I see you may want more than one table. One that stores your
log information. This table might contain log date,logged by,log
statement, etc.. Then create another table that summarizes/counts
how many times you find whatever it is you wish to count. For instance,
if it is a
At 12:14 PM +0100 3/30/07, Tim Bunce wrote:
I've changed the version from '1.0.1' to '1.01' as I'd rather avoid
three-part numbers if we're not using version.pm.
Also I needed to change the elsif to else in the mod_perl2 module
loading code to get it to work for my mod_perl1.
Tim, the best
On Fri, Mar 30, 2007 at 01:47:49PM -0700, Darren Duncan wrote:
At 12:14 PM +0100 3/30/07, Tim Bunce wrote:
I've changed the version from '1.0.1' to '1.01' as I'd rather avoid
three-part numbers if we're not using version.pm.
Also I needed to change the elsif to else in the mod_perl2 module
13 matches
Mail list logo
