[danielkza]

After some tests, I found out SQL_IsNull of SQLX always returns 0. I want to confirm this behavior before sending a bug report. Partial code.

BAN NULL always prints, and I can confirm the column is null by executing the same exact query manually.

PHP Code:

public client_authorized(id)
{
    static szAuth[36]
    get_user_authid(id, szAuth, charsmax(szAuth))
    
    static szQuery[384]
    formatex(szQuery, charsmax(szQuery),
        "SELECT t1.id, online, username, points, admin_flags, ban_reason, (premium_end > NOW()) \
        FROM users AS t1 LEFT OUTER JOIN bans AS t2 \
        ON t1.id = t2.premium_id \
        AND (ban_length=0 OR (timestamp + INTERVAL ban_length MINUTE) >= NOW()) \
        AND auth_cs16='%s'", szAuth )
    
    new iData[1]
    iData[0] = id
    
    SQL_ThreadQuery(g_hSQLTuple, "User_CheckAuth_QueryHandler", szQuery, iData, 1)
}

public User_CheckAuth_QueryHandler(iState, Handle:hQuery, szError, iErrNum, iData[], iDataSize, Float:fTime)
{
    // .... 
    else if(!SQL_IsNull(hQuery,colBanReason))
    {
        server_print("BAN NULL")
        SQL_ReadResult(hQuery, colBanReason, szKickReason, charsmax(szKickReason))
    }
} 


[|PJ| Shorty]

which value has colBanReason?
depending on your SELECT it must be 5

[danielkza]

Originally Posted by |PJ| Shorty which value has colBanReason? depending on your SELECT it must be 5

PHP Code:

enum
{
    colID = 0,
    colOnline,
    colUsername,
    colPoints,
    colAdminFlags,
    colBanReason,
    colPremiumEnd
} 


[|PJ| Shorty]

seems to be a bug then. i never used this function in my plugins.