Catching errors in SQL xlat queries
a.cudbardb at freeradius.org
Fri May 27 04:40:41 CEST 2016
> On 26 May 2016, at 22:14, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> On Thu, May 26, 2016 at 09:13:51PM -0400, Arran Cudbard-Bell wrote:
>> What could we usefully do with a failing string expansion? I
>> guess if it's in an update block and we make updates atomic,
>> then the whole update block could fail.
>> If it's a module configuration item the module could fail...
>> Conditions are weird though.
> Seems like a nasty hack, but create "xlat-Failure := <something>"?
> I don't like it, but it's one way...
Or have conditions return fail. That could be caught and then used to do something else.
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Freeradius-Users