FWIW, this would be a breaking change for SurrealDB without (as far as I can tell) any benefit (the enum discriminant of Value within Id::Array is serialized as 4 big endian bytes so the first byte is always 0x00 and never 0x01).

It might make more sense to not fix this issue and simply warn other users.

If you decide to go with a breaking change - maybe consider swapping the usage of 0x00 and 0x01 so (a, b, c) sequence is less than (a, b, c, d) sequence.

Another idea: you can add 0x00 only if the first byte of an item is 0x01. That won't break SurrealDB, but still fix the issue.

In that case you can use 0x02 instead of 0x00 to also resolve abc < abcd problem.

Another idea: you can add 0x00 only if the first byte of an item is 0x01. That won't break SurrealDB, but still fix the issue.

In that case you can use 0x02 instead of 0x00 to also resolve abc < abcd problem.

Oops, that won't work for items starting with 0x00, sorry