Radiator already provides funtionality to log everything to
an SQL database. There's no hacking required.
Look at the <AuthBy SQL> and the <Log SQL> directives.
The docs are at http://www.open.com.au/radiator/ref.html
I've even posted an example implementation to log accounting
packets into an SQL database while retaining authentication
using another method. Search the mailing list archives.
At 02:29 PM 9/2/99 +0300, Ragnar Kurm wrote:
>
>i'm trying to make radiator to log everything into my database.
>my database table would contain following fields: id, key, value.
>one log event would be grouped by id. how can this be achieved?
>
>nearest solution i can think of is following:
>* hack radiator to provide a perl code to access all event attributes
>* encode them into a long string
>* call database procedure and pass the string
>* the procedure would decode the string and insert key-value pairs
> with shared id into table
>
>is there more elegant way to do this? especially should i hack radiator or
>does it provide facilities to satisfy my needs without hacking one?
>
>
>ragnar
>
>
>===
>Archive at http://www.thesite.com.au/~radiator/
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
