Skip to content

Conversation

@kbennoune
Copy link

No description provided.

mjc-gh and others added 6 commits August 21, 2025 14:56
We'd like to be able to correlate individual queries to any of the EOF
errors we're seeing. This returns the query ID in all of the error
responses so that when we see EOF errors, we can see which specific
queries they occurred on.
kbennoune and others added 8 commits August 22, 2025 10:41
We're getting an EOFError thousands of times a day and ClickHouse has
asked us to give them query IDs to that they can look into it. I
previously put in functionality to add the query ID to the raised error,
but the one place I missed is the one place throwing all the errors.

This sets a query ID that will be used in the HTTP(S) request and will
be in the error message where this is being raised.
…-id-to-error

Add query ID to error message
Fix a syntax error I missed because this library supports older versions
of Ruby (2.7).
…-id-to-error

Fix syntax error due to older Ruby
I called the method passing a Hash at the end, but it was actually a
kwarg named settings. This corrects that call.
The bug is that, for some columns with defaults, the value returned from the DB is "true" instead of the actual value present in the DB. The correct value is returned when the record is reloaded.
…for-default-returning-true

Add workaround for Clickhouse returning `true` for default values on insert.

While the correct default value has never actually been returned from the database, this was silently ignored in Rails 7.x and before. With Rails 8 (specifically rails/rails#53359), the true value starts causing an error for datetime columns (which it should, since true is not valid in such columns).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants