I think there is something weird going on here, FYI. the article linked states
# This is acceptable in ISO 8601 and RFC 3339 ***(with T)***
2019-10-12T07:20:50.52Z
# This is only accepted in RFC 3339 ***(without T)***
2019-10-12 07:20:50.52Z
However I have experienced and just verified again that Dgraph specifically on the GraphQL endpoint (haven’t tested with DQL) errors out if you do not ad the T
So while Dgraph claims to support RFC 3339, it does not correctly according to your linked article at least.
Per RFC 3339 § 5.6: Internet Date/Time Format - (on page 7)
NOTE: ISO 8601 defines date and time separated by “T”. Applications using this syntax may choose, for the sake of readability, to specify a full-date and full-time separated by (say) a space character.
I understand that to say “Applications using this [RFC 3339] syntax may choose”
This “may choose” is by definition up to the decision of the applications implementing the RFC, but linking to above article invalidates this application decision with the blanket statement:
- RFC 3339 is following the ISO 8601 DateTime format. The only difference is RFC allows us to replace “T” with “space”.
This does not clarify that the “us” is the application in this case Dgraph, but leads it to believe the “us” is the developers using said applications.