[Kamailio-Users] BIGINT MySQL problems in 1.5.0.

[Daniel-Constantin Mierla]

Hello,


On 04/03/2009 08:54 AM, Alex Balashov wrote:
> Greetings,
>
> I just installed 1.5.0 and wired it up to a MySQL 5.0.x database, and it 
> appears that I am getting empty/null values for BIGINT columns when 
> accessing them from script.
>
> This is true when I do something like this with SQLOps, for example:
>
>     sql_query("test", "SELECT someBigIntColumn FROM tbl", "ra");
>
>     $var(i) = $dbr(ra=>[0,0]);
>
> $var(i) will have an empty value.
>
> Same will be the case if the access subscript is not [0,0] but say, [0,1].
>
> The problem does not seem to be specific to sqlops;  the same occurs 
> with AVPs:
>
>    avp_db_query("SELECT someBigIntColumn FROM tbl", "$avp(S:bigInt)");
>
> This is also empty.
>
> I did a debug and confirmed that the right value for someBigIntColumn is 
> coming out of the database, and has the right data type.  All that works 
> fine.  However, for some reason this value appears to be invisible 
> within the evaluative scope of the route script.
>
> For now, I am working around it by doing CONVERT(someBigIntColumn, 
> CHAR(20)) inside the query.  However, in principle this means that 
> BIGINT handling is broken.
>
> Has anyone else run into this?  Any insights, or especially, solutions?
>   
pseudo-variables can hold only integer or string values. IIRC, Henning 
added bigint inside the mysql module, but that has not support to upper 
level of script variables.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://www.asipto.com/