Bug: Floats treated as integers and duplicate records not checked when floats used as record id

[Dhghomon]

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.

[
	{
		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';

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?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct