Mysql-ruby returns wrong record count

Ruby
1

Just started using mysql-ruby, and doing a simply query like this:

select distinct rcrdNo from someTable

I’m getting results back from mysql-ruby that is simply not correct.

rcrdNo is a unique random string that’s 20 characters long. The only
thing I can think of is somehow going through mysql-ruby that the full
20 chars is not being considered in DISTINCT?

I can copy/paste the query among different clients, and they all agree
on the records count except for mysql-ruby. In years of using MySQL,
I’ve never come across a discrepency in a query like this through a
client / interface.

Any ideas?

– gw

2

Greg W. wrote:

Just started using mysql-ruby, and doing a simply query like this:
select distinct rcrdNo from someTable
I’m getting results back from mysql-ruby that is simply not correct.

rcrdNo is a unique random string that’s 20 characters long. The only
thing I can think of is somehow going through mysql-ruby that the full
20 chars is not being considered in DISTINCT?

Duh, all I had to do was output the results of each row, and indeed, the
values of rcrdNo are only 13 characters long instead of 20.

What’s up with that?

– gw

3

Greg W. wrote:

Greg W. wrote:

Just started using mysql-ruby, and doing a simply query like this:
select distinct rcrdNo from someTable
I’m getting results back from mysql-ruby that is simply not correct.

rcrdNo is a unique random string that’s 20 characters long. The only
thing I can think of is somehow going through mysql-ruby that the full
20 chars is not being considered in DISTINCT?

Duh, all I had to do was output the results of each row, and indeed, the
values of rcrdNo are only 13 characters long instead of 20.

What’s up with that?

Egads, nevermind. Something funky going on w/data xfr into the test db
I’m using the script on.

Sorry for the noise :stuck_out_tongue:

– gw