TDBC

Attempts to retrieve integers from a table in mysql return what appears to be random gibberish unless the column name of interest is expressed as the argument of a TRIM() function in the SQL query.

Here is the output of "db columns" for a simple straightforward table in a mysql database:

% db columns mytable
a_id {name a_id type integer precision 11 scale 0 nullable 0}

Column a_id contains a small number of rows of three-digit integers.  Try to query one:

% db allrows {SELECT a_id from mytable where a_id=241}
{a_id 3796751089905}

Now enclose column name in a TRIM() function:

% db allrows {SELECT TRIM(a_id) from mytable where a_id=241}
{trim(a_id) 241}

Tcl 8.6b3.

% /usr/bin/mysql --version
/usr/bin/mysql  Ver 14.14 Distrib 5.5.28, for debian-linux-gnu (x86_64) using readline 6.2

I note that the constant returned is 0x00000374000000f1.
My guess is that there's a 32- vs 64-bit glitch going on, because 0x000000f1 is
the desired value of '241'. The fact that I haven't seen it fail on a 32-bit
machine would tend to support this hypothesis.

With the attached patch that adds a naive test, I cannot reproduce on amd64 or i386.

$ mysql --version
mysql  Ver 15.1 Distrib 10.0.30-MariaDB, for OpenBSD (i386) using readline 4.3

$ mysql --version
mysql  Ver 15.1 Distrib 10.0.30-MariaDB, for OpenBSD (amd64) using readline 4.3

$ echo 'puts [info patchlevel]' | tclsh8.6
8.6.6

I, too, am unable to reproduce the symptoms described. I'm presuming that some other fix in the beta cycle resolved the problem.