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
Currently, inserting data into QuestDB follows the Untyped Expression Generation method.
But QuestDB will report errors when the data type is inconsistent. Some of the logs from QuestDB are shown below:
2023-02-10T04:50:23.369319Z I i.q.c.p.PGConnectionContext parse [fd=24, q=INSERT INTO t6(c0) VALUES (0.5653368228661755)] 2023-02-10T04:50:23.369431Z E i.q.c.p.PGConnectionContext error [pos=27, msg=`inconvertible types: DOUBLE -> LONG256 [from=0.5653368228661755, to=c0]`] 2023-02-10T04:50:23.372812Z I i.q.c.p.PGConnectionContext parse [fd=24, q=INSERT INTO t6(c0, c1) VALUES (false, 0.39823032292367677)] 2023-02-10T04:50:23.372920Z E i.q.c.p.PGConnectionContext error [pos=31, msg=`inconvertible types: BOOLEAN -> LONG256 [from=false, to=c0]`] 2023-02-10T04:50:23.374835Z I i.q.c.p.PGConnectionContext parse [fd=24, q=INSERT INTO t4(c0) VALUES (0.044660404052478064)] 2023-02-10T04:50:23.375070Z E i.q.c.p.PGConnectionContext error [pos=27, msg=`inconvertible types: DOUBLE -> BOOLEAN [from=0.044660404052478064, to=c0]`]
This will influence the rate of semantically valid statements.
The type of column and the data should be consistent.
The text was updated successfully, but these errors were encountered:
i can fix this issue . please assign this to me
Sorry, something went wrong.
I want to Fix this Issue. Can I get this.... @MingCheng991129
Hi, please contact @mrigger if you want to be assigned :)
No branches or pull requests
Currently, inserting data into QuestDB follows the Untyped Expression Generation method.
But QuestDB will report errors when the data type is inconsistent. Some of the logs from QuestDB are shown below:
This will influence the rate of semantically valid statements.
The type of column and the data should be consistent.
The text was updated successfully, but these errors were encountered: