Query has unexpected behavior on linux_amd64 about mysql HOT 6 CLOSED

Does this only occur if you run this two queries in that order?
Is the driver on both machines up to date? ( run go get -u github.com/Go-SQL-Driver/MySQL to be sure )
Which server version are you running on your Linux machine?

from mysql.

I tried to get some answers to your question. But the problem becomes even more bizarre. Again, on my laptop darwin_amd64, everything works as expected. When I ssh to any linux_amd64 server and run the mysql CLI manually, my manual queries work as expected. But when I run the exact same Go program, now every Query[Row] reports 0 rows returned.

I'm trying to bundle this into a single reproducible test case. Please stay tuned. Do you test this driver on linux_amd64 against MySQL 5.1.63-rel13.4?

from mysql.

Create a database on MySQL 5.1.63-rel13.4 with one table:

CREATE TABLE `live` (
  `user_id` int(11) NOT NULL,
  `list` text NOT NULL,
  PRIMARY KEY (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

Insert one record:

INSERT INTO live (user_id, list) VALUES (2, "999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999,999999999");

edit: make the list longer, because the real data is bigger than "1,2,3,4,5", and I think it might be the same bug as #38

Save this program as dbtest.go and run with go run dbtest.go -dsn="user:pass@tcp(1.2.3.4:3306)/database_name".

On my laptop (darwin_amd64) it works as expected, printing the list. On my Linux server (linux_amd64) it errors with sql: no rows in result set. Running the latest version of your driver, as retrieved by go get -u -d github.com/Go-SQL-Driver/MySQL in both cases.

from mysql.

This is definitely a bug in the Go-SQL-Driver. This code is exactly the same, but uses the mymysql driver (and a different DSN syntax). Running it yields the expected behavior.

from mysql.

Can you confirm, that the it works now?

from mysql.

Test case confirmed working.

Thanks!

from mysql.