Our patch needs a little work before its ready to be committed. Currently to save auditing the rest of the code we are rewriting null values to "X" which doesn't exist as a user in our database. We will spend some time tomorrow to write this patch correctly now that I know alan doesn't have anything against it. (It was just a hack to get us operational) I also think that we should be able to have DEFAULT data in SQL tables, but this will require a whole new class of query to impliment correctly.(Or a second copy of the SQL module with the current code) Cheers On Wed 20 Sep 2006 19:26, Michael Griego wrote:
How does your patch work, Peter? Is it similar to what I described?
--Mike
On Sep 20, 2006, at 9:45 AM, Alan DeKok wrote:
Peter Nixon <listuser@peternixon.net> wrote:
We have had to locally patch rlm_sql to make it accept NULL usernames. Is there any particular reason why it does this check? rlm_sql_postgresql works fine with NULL usernames as does the rest of FreeRADIUS.
Go for it.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/ devel.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
-- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc