Postgres pgadmin bug

[micnigh]

I recieved this error as well, and it seems to be related to the post here

Localhost port forwarding causing invalid SQL [FIXED]

I expect this issue isn’t actually related to SQL or MySQL. I think this is just highlighting a deeper issue with the way the localhost port forwarding feature works. Expected behavior Running a large piece of SQL from a Java App or MySQL Client (e.g. Toad for MySQL) against a MySQL instance running in Docker via the localhost/127.0.0.1 hostname should return the result set. Actual behavior The SQL that is run isn’t valid when running through localhost and MySQL returns an “You have an error i…

One workaround is to connect to a hostname of ‘docker’ instead of ‘localhost’