(RADIATOR) AcctSQLStatement ONLY AuthBy?

[Mariano Absatz]

El 28 Jul 2001, a las 19:36, Hugh Irvine escribió:

> 
> Hello Mariano -
> 
> You can do what you describe too, by using the AccountingStartsOnly, 
> AccountingStopsOnly and AccountingAlivesOnly tags in the AuthBy SQL 
> clause.
That was (and still is) my intention... the only thing that worried my was the 
following paragraph from section 6.26 of the 2.18.2 release manual (see underlines 
under a fixed text viewer):

> When AuthBy SQL receives an Accounting-Request message, it can store any
> number of the attributes from the request in an SQL table. You can control
> the table it stores in, and the names of the columns where the attributes
> are stored, and the attribute that is stored there. To enable SQL
                                                      ^^^^^^^^^^^^^
> accounting you must define AccountingTable and you must define at least
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> one AcctColumnDef. If you don't do both of these AuthBy SQL will
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> acknowledge Accounting-Request message but will not store them anywhere.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The example goodies/sql.cfg in the Radiator distribution shows a typical
> setup that will work with the table schemas in the goodies directory. 

Re-reading this, this is, in fact true since, in this specific <AuthBy>, I am not 
storing them anywhere, but I am doing something else besides aknowledging them.

> 
> Have a look at section 6.26 in the Radiator manual.