New FreeRADIUS module: rlm_backcounter

[Peter Nixon]

> > Do you plan to add/support different sql databases in future?
>
> No, because I don't need it.
>
> > It's not critical that you do, we thank you for the code contribution
> > either way but at some point someone will try to use postgresql or some
> > other database (me for example :-) and someone will need to support
> > it...
>
> That's how open source works, don't it? Someone who needs some feature
> adds it ;-P
>
> > Same question applies to rlm_netvim_pools...
>
> I don't plan to add support for other rdbms than MySQL (at least in near
> future) in it, either.

I have been attempting to make rlm_sqlhpwippool work with Postgresql. The 
biggest issue so far is the way you define zeroed dates in the sql schema 
like:
 `modified` datetime NOT NULL default '0000-00-00 00:00:00'

Most databases (Postgresql included) do not allow invalid dates like this and 
give "ERROR:  date/time field value out of range". This should with be NULL 
or should default to now() or some date in the distant past. Do you think 
there will be any problems if I set this to:
 modified TIMESTAMP NOT NULL default now()

or simply (Allowing NULLS):
 modified TIMESTAMP

Cheers
-- 

Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc