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
We are hoping that the token expiry (from connection key Auth_Expires) can be represented as a Unix timestamp in seconds as opposed to "ISO 8601 datetime with timezone".
The reason being that it may be easier to handle Unix time as an absolute point in time rather than to use actual timestamps according to ISO 8601. It would also be clearer, and be less prone to error for users of the ODBC spec. Also in regards to OAuth, it will be easier to translate the token expiry (in seconds) into unix timestamp format (in seconds).
Thanks,
Drew
The text was updated successfully, but these errors were encountered:
Hi,
We are hoping that the token expiry (from connection key Auth_Expires) can be represented as a Unix timestamp in seconds as opposed to "ISO 8601 datetime with timezone".
The reason being that it may be easier to handle Unix time as an absolute point in time rather than to use actual timestamps according to ISO 8601. It would also be clearer, and be less prone to error for users of the ODBC spec. Also in regards to OAuth, it will be easier to translate the token expiry (in seconds) into unix timestamp format (in seconds).
Thanks,
Drew
The text was updated successfully, but these errors were encountered: