Re: (RADIATOR) SQL Accounting / Radius Attribute Values only

2002-01-04 Thread Hugh Irvine
Hello Robert - I can't think of an easy way to do what you describe below, other than writing a custom hook to add some pseudo-attributes to the current request for the integer values you require, and then using them in the AcctSQLStatement. There are some example hooks in the distribution i

RE: (RADIATOR) SQL Accounting / Radius Attribute Values only

2002-01-04 Thread Robert Blayzor
;%{Acct-Input-Octets}','%{Acct-Output-Octets}','%{Acc t-Session-Time}' A more advanced SQL statement? -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] > -Original Message----- > From: Hugh Irvine [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 03, 2002 11:38 P

Re: (RADIATOR) SQL Accounting / Radius Attribute Values only

2002-01-03 Thread Hugh Irvine
Hello Robert - You can do this with AcctColumnDef's: AcctColumnDef NASPORT,NAS-Port,integer Have a look at section 6.28.13 in the Radiator 2.19 reference manual. regards Hugh On Fri, 4 Jan 2002 13:43, Robert Blayzor wrote: > > My first inclination would be to archive the accounting

RE: (RADIATOR) SQL Accounting / Radius Attribute Values only

2002-01-03 Thread Robert Blayzor
> My first inclination would be to archive the accounting data > on a periodic > basis (every day, every week, every month, whatever). One > easy way to do this > is to set up a different table for each month (week, day, > whatever) for > example and then use the Radiator special characters

Re: (RADIATOR) SQL Accounting / Radius Attribute Values only

2002-01-03 Thread Hugh Irvine
Hello Robert - My first inclination would be to archive the accounting data on a periodic basis (every day, every week, every month, whatever). One easy way to do this is to set up a different table for each month (week, day, whatever) for example and then use the Radiator special characters