-
Notifications
You must be signed in to change notification settings - Fork 272
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
Add support for QuestDB #457
Comments
I ran the code of QuestDB and found that the correctness rate |
I think it would be useful to analyze which statements are failing. The rate definitely seems low. @SuriZhang, do you have any idea? |
Not sure why this happens. But iirc, maybe this shouldn’t be run using multiple threads(at least I didn’t do that)? I can have a quick check later.
可用于iOS的myMail发送
2023年1月29日 星期日 +0800 下午1:53 发件人 ***@***.*** ***@***.***>:
…I think it would be useful to analyze which statements are failing. The rate definitely seems low. @SuriZhang , do you have any idea?
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <sqlancer/sqlancer/issues/457/1407569950 @ github . com>
|
@MingCheng991129 discovered that the number of tables referenced in queries is very high, so that might be the issue. |
@MingCheng991129 pls see #712 . this might give you some ideas on the limitation of the current (and very preliminary) version of support of questDB in sqlancer. |
See questdb/questdb#595.
The text was updated successfully, but these errors were encountered: