New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors from sql-server #4827
Comments
Thanks for reporting this one @ericmock. Can you share any more details about the Java connection layer you're using? Is it just over the standard MySQL ConnectorJ JDBC library, or is there another library/tool in there somewhere? @jennifersp – could you try to repro this one today? Adding it to the client integration tests could be an easy way to run it over a JDBC connection. |
I'm just using DBeaver (on Manjaro). The error log is below if it's useful. Since updating to the latest version, I'm seeing this quite often (but seemingly randomly). This was one case where I could reliably reproduce.
|
Perfect! This is super helpful; thank you! We'll try to repro with DBeaver. I also notice that DBeaver is using the MariaDB JDBC driver. We have Java tests with the MySQL ConnectorJ driver, but I'm not sure that we have tests for the MariaDB driver. We'll look into adding that as well. |
FYI... org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error [08S01]: Communications link failure The last packet successfully received from the server was 6 milliseconds ago. The last packet sent successfully to the server was 7 milliseconds ago. The last packet successfully received from the server was 6 milliseconds ago. The last packet sent successfully to the server was 7 milliseconds ago. The last packet successfully received from the server was 6 milliseconds ago. The last packet sent successfully to the server was 7 milliseconds ago. |
Same issue. Works without the |
Hi @ericmock, thank you for issuing this bug! I found where the issue is coming from and will get the fix in as soon as I can. |
The fix will be merged into dolt very soon, and it will be out in the next Dolt release. A workaround for this bug is that you can set arbitrary limit (that is bigger than the number of query result) without offset for the query; for example,
|
Great work! |
Fixed by dolthub/go-mysql-server#1414 |
This may just be the particular Java connection layer I'm using, but when I do:
select homepage_url, count(*) as cnt from hospitals h where chargemaster_indirect_url is null group by homepage_url;
everything is fine. However, when I do
select homepage_url, count(*) as cnt from hospitals h where chargemaster_indirect_url is null group by homepage_url order by cnt;
I get "Socket error"
The text was updated successfully, but these errors were encountered: