On 12 Oct 2012, at 13:23, Stefano Zanmarchi <zanmarchi@gmail.com> wrote:
Exactly what I needed. Just one more thing. Why does the mysql log show that the query performed with XLAT is now performed 3 times in a row per access request? Thank you, Stefano
[output from mysql:] 121012 14:20:39 394 Query SELECT count(*) FROM eduroam_mac_registrati AS m, eduroam_diritto_uso AS d WHERE m.username = d.username AND m.mac='98-4b-4a-f5-bf-41' and d.diritto='S' 393 Query SELECT count(*) FROM eduroam_mac_registrati AS m, eduroam_diritto_uso AS d WHERE m.username = d.username AND m.mac='98-4b-4a-f5-bf-41' and d.diritto='S' 392 Query SELECT count(*) FROM eduroam_mac_registrati AS m, eduroam_diritto_uso AS d WHERE m.username = d.username AND m.mac='98-4b-4a-f5-bf-41' and d.diritto='S'
Sent pull request to fixup that code a bit. The authorize query will now just go ahead and run the reply query and the rest of the queries if authorize_check_query is null. There are still some advantages to using the proper reply table and the sql module (adding multiple reply attributes for example). -Arran