ejabberd 1.1.3: Security fix on mod_roster_odbc

Okay, after just upgrading ejabberd from 1.1.2 to 1.1.3 we have not working roster at all...
What da f*ck?
=ERROR REPORT==== 2007-06-01 15:47:03 ===
E(<0.287.0>:ejabberd_hooks:187): {function_clause,
[{mod_roster_odbc,
raw_to_record,
["server.com",
{"user",
"999939393@icq.server.com",
[],
"B",
"N"}]},
{mod_roster_odbc,
'-get_in_pending_subscriptions/3-fun-1-',
2},
{lists,flatmap,2},
{mod_roster_odbc,
get_in_pending_subscriptions,
3},
{ejabberd_hooks,run_fold1,4},
{ejabberd_c2s,
resend_subscription_requests,
1},
{ejabberd_c2s,presence_update,3},
{ejabberd_c2s,session_established,2}]}
running hook: {resend_subscription_requests_hook,["user","server.com"]}

investigation showed, when rosterusers table gets cleared, new users can be added without any problem.

that means, that we should blame developers... they've done stupid things with NULL analysis...

the solution is one-string (for postgresql)

update rosterusers set askmessage = '', subscribe = '';

Again, and again... everything is done through anus....