From: Anton <anton.vazir@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Pierre Chifflier <chifflier@inl.fr>,
netfilter-devel@vger.kernel.org, Eric Leblond <eric@inl.fr>
Subject: Re: [ULOGD PATCH 2/4] Add label option (SQL part)
Date: Wed, 30 Apr 2008 09:34:40 +0500 [thread overview]
Message-ID: <200804300934.41520.anton.vazir@gmail.com> (raw)
In-Reply-To: <48142E71.7000802@netfilter.org>
Just IMHO,
String is more visual and understandable for human view, but
for how much of the actual processing of the loged data
done by hands? I suppose majority is somehow automated,
scripted, etc. Integer allows much faster inserts, in-DB
processing and lower traffic. I would vote for interger :)
Regards,
Anton.
On Sunday 27 April 2008 12:42, Pablo Neira Ayuso wrote:
> Pierre Chifflier wrote:
> > This patch adds support for "label" option in the SQL
> > schema. For example, it can be used by another module
> > to determine if the packet has been dropped, rejected
> > or accepted.
>
> I have kept this back until we discuss if it would be
> better to have a string instead of an integer.
next prev parent reply other threads:[~2008-04-30 4:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:58 Database update: add label, update views and conntrack Pierre Chifflier
2008-04-21 21:58 ` [ULOGD PATCH 1/4] Convert INSERT_CT to a function, returning the id (MySQL) Pierre Chifflier
2008-04-27 7:42 ` Pablo Neira Ayuso
2008-04-21 21:58 ` [ULOGD PATCH 2/4] Add label option (SQL part) Pierre Chifflier
2008-04-27 7:42 ` Pablo Neira Ayuso
2008-04-30 4:34 ` Anton [this message]
2008-04-30 8:40 ` Pablo Neira Ayuso
2008-04-21 21:58 ` [ULOGD PATCH 3/4] Add function and some view to display IP addresses as strings (MySQL) Pierre Chifflier
2008-04-27 7:43 ` Pablo Neira Ayuso
2008-04-21 21:58 ` [ULOGD PATCH 4/4] Add function INSERT_CT for conntrack (PostgreSQL) Pierre Chifflier
2008-04-27 7:44 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804300934.41520.anton.vazir@gmail.com \
--to=anton.vazir@gmail.com \
--cc=chifflier@inl.fr \
--cc=eric@inl.fr \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox