We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In version 1.7.10, it is observed that when limiting a select to specific columns, the database occasionally misses a few records in the response.
The following are logs for the same query fired twice on the same table. The query was expected to respond with 2 records on both occasions.
blobcity>sql test: select col1, col2 from test.test {"p":[{"col2":2,"col1":1}],"time(ms)":24,"ack":"1","rows":1} blobcity>sql test: select col1, col2 from test.test {"p":[{"col2":4,"col1":2},{"col2":2,"col1":1}],"time(ms)":3,"ack":"1","rows":2}
However, the following queries deliver consistent results select col1 from test.test select * from test.test
select col1 from test.test
select * from test.test
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In version 1.7.10, it is observed that when limiting a select to specific columns, the database occasionally misses a few records in the response.
The following are logs for the same query fired twice on the same table. The query was expected to respond with 2 records on both occasions.
However, the following queries deliver consistent results
select col1 from test.test
select * from test.test
The text was updated successfully, but these errors were encountered: