We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This means inserting a date like 2018-09-14T12:33:21.831371900 will be stored and later retreived as 2018-09-14T12:33:21.
2018-09-14T12:33:21.831371900
2018-09-14T12:33:21
This is caused by us using SQLT_DAT as host type, which doesn't have below second precision.
SQLT_DAT
Using SQLT_CHR and use the standard string representation to convert between NativeDateTime and Timestamp.
SQLT_CHR
NativeDateTime
Timestamp
Need to set NLS_TIMESTAMP_FORMAT to set the format correctly. Like so:
NLS_TIMESTAMP_FORMAT
ALTER SESSION SET NLS_TIMESTAMP_FORMAT = 'YYYY-MM-DD"T"HH:MI:SS.FF';
Using SQLT_TIMESTAMP and OCIDateTime .
SQLT_TIMESTAMP
OCIDateTime
https://docs.oracle.com/database/121/LNOCI/oci12oty.htm#LNOCI16842
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This means inserting a date like
2018-09-14T12:33:21.831371900
will be stored and later retreived as2018-09-14T12:33:21
.This is caused by us using
SQLT_DAT
as host type, which doesn't have below second precision.Possible solution 1: Use strings
Using
SQLT_CHR
and use the standard string representation to convert betweenNativeDateTime
andTimestamp
.Need to set
NLS_TIMESTAMP_FORMAT
to set the format correctly. Like so:Possible solution 2: Use oci datetime class
Using
SQLT_TIMESTAMP
andOCIDateTime
.https://docs.oracle.com/database/121/LNOCI/oci12oty.htm#LNOCI16842
The text was updated successfully, but these errors were encountered: