MaxScripting MySQL "SELECT * ..." query thru ODBC 8 returns bizarre results.

MaxScripting MySQL "SELECT * ..." query thru ODBC 8 returns bizarre results.

kolsen
Advocate Advocate
1,013 Views
2 Replies
Message 1 of 3

MaxScripting MySQL "SELECT * ..." query thru ODBC 8 returns bizarre results.

kolsen
Advocate
Advocate

I have a small table in MySQL with 4 records of four columns each.

If I try to select all (*) through a SELECT query, four records come back, but it's the first record, and then the fourth record repeated three times.

If I try the query on a table of two records, I get the first and second record. Yay.

If I try the query on a table of three records, I get the first record and the third record two times.

This has led me to tentatively conclude that this is not the typical operator error (i.e., me), and may be due to some limit in the ODBC Driver (8).

 

I'll move on to use the .NET dll someday, but I was wondering if anyone has any insight to this odd result. Some research turned up the attached page, which advises (at the very bottom) only to access tables on a per record basis. I wonder why...

 

cheers, 

KO

0 Likes
Accepted solutions (1)
1,014 Views
2 Replies
Replies (2)
Message 2 of 3

kolsen
Advocate
Advocate
Accepted solution

Bizarre UPDATE:

After ignoring the problem for a week I started looking into using .NET.  Just for fun, ran the old script version that wasn't working and it worked fine. No changes to the script at all. It may have been a driver issue, but who knows. Onward.

0 Likes
Message 3 of 3

Anonymous
Not applicable

i realize this is old, but have you learned anything new about this? i'm having the same issue. The query works fine in 2017 but not in 2019 or 2020.

0 Likes