SQL module question...

[Alan DeKok]

On Apr 20, 2015, at 5:17 AM, Stefan Paetow <Stefan.Paetow at jisc.ac.uk> wrote:
> I know that there've been several changes to how the sql module loads. On one site, there is only one query, in a sql xlat, and the question is now about an error that the site is getting:
> 
> (14) sql: EXPAND .query
> (14) sql:    --> .query
> No such configuration item .query
> 
> Granted, all table entries and the '$INCLUDE' for query.conf were commented out on the basis that only the sql xlat would be used, but why would the xlat still be looking for the 'post-auth.query' entry in the sql module (or the query.conf for that matter)?

  Because the module has no idea which sections it will be called from in the future.  There's no "instantiate post-auth stuff" method.  Just "instantiate everything".

> We've gotten around it by defining a 'post-auth { query = "select * from ..." }' line in the sql module to make it happy, but it seems to me that if you use a sql xlat, and there is no other call to 'sql' or '-sql' in the post-auth section, it shouldn't be looking for the post-auth.query string... 

  Ideally, yes.  That's hard to do without changing significant amounts of the server.

  Alan DeKok.