Eric Leblond wrote: > Hello, > > On Saturday, 2008 April 5 at 17:05:16 +0200, Pablo Neira Ayuso wrote: >> Eric Leblond wrote: >>> This patch suppress a now unused option. Each database module >>> have now to be used with a defined IP storage type. >> As far as I can remember, this parameter was introduced because some >> sysadmins queried the sql database directly to look for certain IPs. I >> know that this isn't good for performance but it has some clients in >> ulogd 1.x. >> >> Does mysql have something like the PgSQL's inet type? > > No, there is no advanced types in MySQL. > >> Looking at the >> database definitions, we are storing the IPs in binary format in mysql >> and in inet type in PgSQL. Does this mean that there's no replacement >> for the ip_as_string in mysql? > > I think it could be achieved by working on a VIEW which could display > the binary field in IP string format. An other solution could be to > provide two database schemas (as it was before). I prefer the view option. > In any cases, it is not related to ulogd C code: the list of keys (with > their associated type) is given by the content of a table. Thus, there > is no need for the option ip_as_string. OK. Applied, thanks. -- "Los honestos son inadaptados sociales" -- Les Luthiers -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
