Hello all!

With version 0.4 I had problems with sql authorization, but it was fixed in 0.5
version, and I forgot about that problem.
But now I have problems with sql_xlat function and started to look in the code.
The problem occurs only with oracle driver, with mysql it works fine.

Well, I find something strange in sql_xlat function.
Look:
After sql_fetch_row, there is a call sql_finish_select_query, but this function
(in oracle) frees result's memory. After calling sql_finish_select_query,
sql_xlat
tries to use results, but the I wonder, how it can use it, if it's memory
released.

I commented sql_finish_selelect_query it function start to work fine both with
oracle
and mysql. I don't know the purpose of this function in mysql variant, but I'm
sure that
in oracle variant it is placed in wrong place.
Perhaps without this function there will be memory leak, I've not checked.
If someone who, develop sql functions, care about functionality of sql
functions, he
should fix it. Or if no one care, can anybody tell me what is purpose of
sql_finish_select_query function and I'll fix it byself.

----=====----
Yuri Bazhukov


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to