So, here is the scenario: 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? 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... :-/ Thoughts (on the approach) and the aide memoire are very much appreciated. :-) With Regards Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.