Topic: OCI Direct Path Load API and SQLT_TIMESTAMP
Actually a question
The documentation unambiguously hints that SQLT_TIMESTAMP is supported in OCI Direct Path API. As 187th code.
But to push it in a database it was possible only specifying 180th code, peeping it in DUMP ()
On 187th falls, speaking about conversion errors and though you burst.
With other types (SQLT_NUM, SQLT_TIMESTAMP_TZ, SQLT_TIMESTAMP_LTZ) such tricks it is not watched.
To greater surprise intensive , and did not produce generally any examples in this respect, from a word generally anything.
All native examples and demos from Oracle show how to work only with SQLT_CHR
Sketchy review of any libraries (FireDAC/AnyDAC, DOA, ODAC) showed and at all any rudimentary development in this question - in them is supported only SQT_DAT (i.e. DATE), about TIMESTAMP generally anything.
Can at whom there are examples as it is necessary to work correctly with TIMESTAMP Direct Path Loading OCI API?
No, not that that absolutely is necessary, hands it was possible to me, but doubts that it in any way not documentary method turned out, it guards.