Bug#41890: marked as done (libapache-dbilogger-perl: Incompatible with PostgreSQL due to unquoted column names)
Debian Bug Tracking System
owner@bugs.debian.org
Mon, 07 Mar 2005 15:48:09 -0800
Your message dated Mon, 07 Mar 2005 18:33:25 -0500
with message-id <E1D8Rj3-00019o-00@newraff.debian.org>
and subject line Bug#41890: fixed in libapache-dbilogger-perl 0.93-6
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 25 Jul 1999 15:28:48 +0000
Received: (qmail 3934 invoked from network); 25 Jul 1999 15:28:47 -0000
Received: from durham1-151.dsl.gtei.net (4.3.1.151)
by master.debian.org with SMTP; 25 Jul 1999 15:28:47 -0000
Received: from juliet.private.net (juliet.private.net [192.168.1.2])
by durham1-151.dsl.gtei.net (Postfix) with ESMTP id 43264FA811
for <submit@bugs.debian.org>; Sun, 25 Jul 1999 11:28:47 -0400 (EDT)
Received: by juliet.private.net (Postfix, from userid 1000)
id 8D627CB825; Sun, 25 Jul 1999 11:27:52 -0400 (EDT)
Sender: mdorman@juliet.private.net
To: submit@bugs.debian.org
Subject: [Chris McClimans <chris@mcclimans.net>] libapache-dbilogger-perl with postgresql
From: Michael Alan Dorman <mdorman@gte.net>
Date: 25 Jul 1999 11:27:52 -0400
Message-ID: <87btd03g1z.fsf@juliet.private.net>
Lines: 68
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Package: libapache-dbilogger-perl
X-From-Line: chris@mcclimans.net Sat Jul 24 15:15:31 1999
Return-Path: <chris@mcclimans.net>
Delivered-To: mdorman@localhost.private.net
Received: from localhost (localhost [127.0.0.1])
by juliet.private.net (Postfix) with ESMTP id 45578CB822
for <mdorman@localhost>; Sat, 24 Jul 1999 15:15:31 -0400 (EDT)
Received: from mail.gte.net
by localhost with POP3 (fetchmail-5.0.5)
for mdorman@localhost (single-drop); Sat, 24 Jul 1999 15:15:31 -0400 (EDT)
Received: from master.debian.org ([209.41.108.5]) by mail2.mailsrvcs.net
(InterMail v03.02.04 118 119) with SMTP
id <19990724191210.STVC1382416@master.debian.org>
for <mdorman@gte.net>; Sat, 24 Jul 1999 14:12:10 -0500
Received: (qmail 19868 invoked by uid 856); 24 Jul 1999 19:15:32 -0000
Delivered-To: mdorman@debian.org
Received: (qmail 19811 invoked from network); 24 Jul 1999 19:15:31 -0000
Received: from unknown (HELO center.oftheInter.net) (qmailr@24.219.7.132)
by master.debian.org with SMTP; 24 Jul 1999 19:15:31 -0000
Received: (qmail 7825 invoked by uid 1000); 24 Jul 1999 21:59:58 -0000
Date: Sat, 24 Jul 1999 16:59:58 -0500
From: Chris McClimans <chris@mcclimans.net>
To: Michael Alan Dorman <mdorman@debian.org>
Subject: libapache-dbilogger-perl with postgresql
X-Gnus-Mail-Source: file:/var/spool/mail/mdorman
Message-ID: <19990724165958.A5609@mcclimans.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
Lines: 35
Xref: juliet.private.net personal:1216
I was looking at your dbilogger package and wanted to get it to work with
postgresql. One problem I came accross is that the column name 'user' is a
SQL92 reserved word. Because of this I am unable to create a column
called 'user' in my postgresql requests table. I also noticed that usertrack
and contenttype are missing from the table def in
/usr/doc/libapache-dbilogger-perl/README. These columns appear to be required
when inserting normal request from the current apache setup in potato.
>From http://www.postgresql.org/docs/user/syntax.htm#AEN348
The following are Postgres reserved words which are also SQL92 or SQL3
reserved words: (... text ommitted ...) USER
So I changed the 'user' column to 'username' and added the two new fields.
There is no requirement to make new 'id' entries in postgresql as it keeps
track of unique columns via oids so I didn't use it.
Here is my postgresql table:
CREATE TABLE requests (
server varchar(127) DEFAULT '' NOT NULL,
bytes int4 DEFAULT '0' NOT NULL,
username varchar(15), filename varchar(200), remotehost varchar(150),
remoteip varchar(15) DEFAULT '' NOT NULL,
status int4 DEFAULT '0' NOT NULL,
timeserved datetime DEFAULT '1900-01-01 00:00:00' NOT NULL,
urlpath varchar(200) DEFAULT '' NOT NULL,
referer varchar(250), useragent varchar(250),
usertrack varchar(250), contenttype varchar(250)
);
Would it be appropriate to add a reference to this table and modify the
current dbilogger to not use the reserved word 'user'.
Thanks for any feedback and for letting me take up your time.
-chris
---------------------------------------
Received: (at 41890-close) by bugs.debian.org; 7 Mar 2005 23:38:32 +0000
>From katie@ftp-master.debian.org Mon Mar 07 15:38:32 2005
Return-path: <katie@ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D8Rnz-0000g1-00; Mon, 07 Mar 2005 15:38:32 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1D8Rj3-00019o-00; Mon, 07 Mar 2005 18:33:25 -0500
From: Gunnar Wolf <gwolf@debian.org>
To: 41890-close@bugs.debian.org
X-Katie: $Revision: 1.55 $
Subject: Bug#41890: fixed in libapache-dbilogger-perl 0.93-6
Message-Id: <E1D8Rj3-00019o-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Mon, 07 Mar 2005 18:33:25 -0500
Delivered-To: 41890-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: libapache-dbilogger-perl
Source-Version: 0.93-6
We believe that the bug you reported is fixed in the latest version of
libapache-dbilogger-perl, which is due to be installed in the Debian FTP archive:
libapache-dbilogger-perl_0.93-6.diff.gz
to pool/main/liba/libapache-dbilogger-perl/libapache-dbilogger-perl_0.93-6.diff.gz
libapache-dbilogger-perl_0.93-6.dsc
to pool/main/liba/libapache-dbilogger-perl/libapache-dbilogger-perl_0.93-6.dsc
libapache-dbilogger-perl_0.93-6_all.deb
to pool/main/liba/libapache-dbilogger-perl/libapache-dbilogger-perl_0.93-6_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 41890@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gunnar Wolf <gwolf@debian.org> (supplier of updated libapache-dbilogger-perl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 7 Mar 2005 17:15:31 -0600
Source: libapache-dbilogger-perl
Binary: libapache-dbilogger-perl
Architecture: source all
Version: 0.93-6
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Changed-By: Gunnar Wolf <gwolf@debian.org>
Description:
libapache-dbilogger-perl - Tracks what's being transferred in a DBI database
Closes: 41890
Changes:
libapache-dbilogger-perl (0.93-6) unstable; urgency=low
.
* Documented how the table should be used in PostgreSQL, added a small
patch (Thanks, Julian Mehnle!) preventing the problem from
happening. (Closes: #41890)
Files:
1d9b7e6b1811c4030df90051fb02da6a 790 perl optional libapache-dbilogger-perl_0.93-6.dsc
a8f5732fd48e209fe514b10ebe81fd4f 2661 perl optional libapache-dbilogger-perl_0.93-6.diff.gz
dab89f70f5f472122874fb96b59430aa 12548 perl optional libapache-dbilogger-perl_0.93-6_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCLOG22A7zWou1J68RAkuUAJ0Y22RXpXXUv7461dfEAJEJUFPmZACaAhpm
CUzun/nSWEJDUZ35loh2CsE=
=Eazh
-----END PGP SIGNATURE-----