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
Describe the bug
Truncating the date string into milliseconds without the nanoseconds, prevents us from querying the record since the entire timestamp is recorded. The query works within SurrealDB but since the format is slightly off, this prevents us from obtaining specific record data.
To Reproduce
Steps to reproduce the behavior:
Create a test record with a complex id of a timestamp inside Surrealist. Note the id. CREATE ONLY Test:[time::now()] SET data="some data"
Run the select statement in the surreal CLI on the specific record. Note the id here. SELECT * FROM Test
Compare ids. The precision of the id prevents us from querying the id on the database. SELECT * FROM $testId
Expected behavior
The full string for the date should be displayed. This should occur in all datetime display locations(ie query result, id inputfield). If users wish for a shorter format, the user should have the data itself be represented by fewer digits (ie. use time::round(datetime, 1ms)).
Environment:
The text was updated successfully, but these errors were encountered:
Describe the bug
Truncating the date string into milliseconds without the nanoseconds, prevents us from querying the record since the entire timestamp is recorded. The query works within SurrealDB but since the format is slightly off, this prevents us from obtaining specific record data.
To Reproduce
Steps to reproduce the behavior:
CREATE ONLY Test:[time::now()] SET data="some data"
SELECT * FROM Test
SELECT * FROM $testId
Expected behavior
The full string for the date should be displayed. This should occur in all datetime display locations(ie query result, id inputfield). If users wish for a shorter format, the user should have the data itself be represented by fewer digits (ie. use time::round(datetime, 1ms)).
Environment:
The text was updated successfully, but these errors were encountered: