You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The models.ID.String() function appears to be removing these characters (⟨⟩), which causes discrepancies when working with IDs programmatically.
I would like to bring to your attention a concern regarding the use of the character pair ⟨⟩ in record IDs, particularly when IDs contain special characters. While these characters may serve a purpose, they are not easily typeable using a standard keyboard, especially on systems like ThinkPad laptops that lack a numeric keypad. This makes manual interaction with such IDs inconvenient.
Steps to reproduce
Create a record in SurrealDB with special characters in the ID.
Fetch the record using the Go SDK.
Observe that models.ID.String() strips out ⟨⟩ from the ID, making it inconsistent with the actual stored record ID.
Expected behaviour
Those special chars should be retained in the string format of the ID
Describe the bug
The models.ID.String() function appears to be removing these characters (⟨⟩), which causes discrepancies when working with IDs programmatically.
I would like to bring to your attention a concern regarding the use of the character pair ⟨⟩ in record IDs, particularly when IDs contain special characters. While these characters may serve a purpose, they are not easily typeable using a standard keyboard, especially on systems like ThinkPad laptops that lack a numeric keypad. This makes manual interaction with such IDs inconvenient.
Steps to reproduce
Create a record in SurrealDB with special characters in the ID.
Fetch the record using the Go SDK.
Observe that models.ID.String() strips out ⟨⟩ from the ID, making it inconsistent with the actual stored record ID.
Expected behaviour
Those special chars should be retained in the string format of the ID
SurrealDB version
Go SDK 0.3.2, windows 11
Contact Details
[email protected]
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: