Bug: DateTimes are not inserted into the database correctly

[Du-z]

Continuation of #25

Datetimes still are inserted with the fraction portion of the date prepended with two zeros. Tests seem to work as expected, despite the data being wrong.

[ProphetLamb]

Thanks for the report, I've read the discussion on discord about this bug.

I reviewed the current implementation and found the following issues in addition to your report:

1. The current implementation for DateTime is entirely based on serializing a DateOnly followed by a TimeOnly.
2. All DateTime and DateTimeOffset instances are converted to UTC (Z suffix) serializing a specific timezone (+02 or -06) is not supported.
3. The serializer cannot handle integers represented in variable length, e.g. 4 instead of 04.

[StephenGilboy]

This should be fixed in SurrealDB now. surrealdb/surrealdb#250

[ProphetLamb]

True, sadly, the changeset is not in the current beta release.
We could change our CI to compile SurrealDB from source, but that doesn't represent the average user. So we'll have to wait with the issue, until the next surrealdb release :(

@tobiemh do you have any information on the release schedule of SurrealDB? Is there a high velocity release channel, something like nightly/weekly, in the works?

[Du-z]

We can this bug open (tagged as blocked maybe?) and keep the tests commented. When the the update rolls out we can un-comment them and close this issue.

[ProphetLamb]

Blocked until surrealdb/surrealdb#250 is in release

[tobiemh]

Hi @ProphetLamb , I've added a nightly release so that the main branch is released daily. This should be going live midnight tonight UTC time!

[ProphetLamb]

Neat! Thanks a lot, makes developing much easier.

[ProphetLamb]

Solved with #52