Defining multiple post-auth INSERT queries for the same table
Alan DeKok
aland at deployingradius.com
Tue May 16 18:16:38 CEST 2017
On May 16, 2017, at 12:04 PM, Stefan Paetow <Stefan.Paetow at jisc.ac.uk> wrote:
>
> We've been asked to provide CUI-style backing for the Moonshot-*-TargetedId functionality in FreeRADIUS. Since this originates from us, I thought it might be more useful to simply use *one* column for the pre-requisite GSS-Acceptor-* and the Trust-Router-COI attributes (i.e. mix and mingle). But now, for the life of me, I can't remember for the life of me how to define multiple queries in one sql instance. Do I simply name them (i.e. name_of_query = 'query here...') and then just invoke them in their appropriate section?
It depends on what you want to do. What's the schema and use-case?
The current code does one query for authentication, and multiple possible insert / updates for accounting.
> Or, since many here use databases, would you prefer using a table that includes a column for the appropriate attribute (even if it's not used for the retrieval)? That seems like an awful waste of space and data to me... :-/
I'm not sure what these things are used for, so I don't know.
Alan DeKok.
More information about the Freeradius-Users
mailing list