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
As to the second phrase of the topic: I've understood that any references to "Milliseconds" (and correspoding API names) in the Interval type documentation should be read as "Nanoseconds", according to Oracle documentation.
Thanks for reporting this !
In older Oracle versions, OCI documentation for OCIIntervalGetDaySecond() and OCIIntervalSetDaySecondl() refered to 'fractional part of second' and not "nanoseconds" in more recent ones.
Thus :
I updated documentation of the C and C++ APIs to precise it is nano seconds (no code change in C API)
I added Interval::GetNanoSeconds() and Interval::SetNanoSeconds() that behave as previous Inverval::GetMilliSeconds() and Inverval::SetMilliSeconds()
I modified Inverval::GetMilliSeconds() and Inverval::SetMilliSeconds() with a multiplier and divider factor
Hello,
Suppose, I have a code:
And I have the output as a result set:
In the Oracle SQL Developer the command desc products1;
shows the following:
So, I probably should see:
I am somehow loosing milliseconds.
Can you hint what is wrong with my code?
Thanks.
p.s.
In Oracle SQL Developer I do not see milliseconds as well, but I do see +xx format of the days.
The text was updated successfully, but these errors were encountered: