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
Floats are treated as ints for record ids, and
CREATE person SET id = 9.8, name = 'Mr. 9.8'; CREATE person SET id = 9.8, name = 'Mr. 9.8';
The output will always be the same, and no error generated that a person:9 already exists.
person:9
[ { id: person:9, name: 'Mr. 9.8' } ]
Interestingly, the same behaviour happens if you specify fewer fields than the existing record:
CREATE person SET id = 9.8;
But it will recognize the id as a duplicate if you change the field value or specify another field.
CREATE person SET id = 9.8, name = 'Mr. 9.8'; CREATE person SET id = 9.8, other = 'other'; CREATE person SET id = 9.8, name = 'Something else';
Probably an error that floats can't be used unless enclosed in backticks, like this: CREATE person:9.8;
9.8
1.5.0 for windows on x86_64
Slack
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Floats are treated as ints for record ids, and
Steps to reproduce
CREATE person SET id = 9.8, name = 'Mr. 9.8';
CREATE person SET id = 9.8, name = 'Mr. 9.8';
The output will always be the same, and no error generated that a
person:9
already exists.Interestingly, the same behaviour happens if you specify fewer fields than the existing record:
CREATE person SET id = 9.8;
But it will recognize the id as a duplicate if you change the field value or specify another field.
Expected behaviour
Probably an error that floats can't be used unless enclosed in backticks, like this: CREATE person:
9.8
;SurrealDB version
1.5.0 for windows on x86_64
Contact Details
Slack
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: