Hi, are there any known limitations in direct mode in comparison to client mode? My attempt to use torachangenotification in direct mode failed... is it not supported from odac or from oracle? are there more limitations?
Thanks.
direct mode limitations?
i've found following limitations:
but i can't see anything about change notification...?Comparison of Client mode vs. Direct mode
Applications that use Client mode and those that use Direct mode have similar size and performance. The security of using the Direct mode is the same as using Client without Oracle Advanced Security. ODAC in Direct mode uses DES authentication and does not now support Oracle Advanced Security.
Advantages of using Direct mode
Installation and administration of Oracle client software are not required.
System requirements are reduced.
Direct mode limitations
Connect using TCP/IP protocol only
Some types are not available, like OBJECT, ARRAY, REF, XML, BINARY_DOUBLE, BINARY_FLOAT.
The RowsAffected property is not returned correctly for queries with RETURNING clause
TOraLoader direct loading is not supported.
Certain problems may occur when using firewalls.
Direct mode does not support NLS conversion on the client side.
Transparent Application Failover is not supported.
statement caching is not available.
OS authentication and changing expired passwords features are not available.
We do not guarantee stability of multithreaded applications. It is highly recommended to use separate TOraSession component for each thread when using ODAC from different threads.
Please note that we do not guarantee ODAC Direct mode compatibility with all Oracle servers and in every network. We have tested Direct mode for all versions of Oracle servers for Windows and Linux since 7.3 on a local network. Other platforms may cause some incompatibility issues.
Connecting in Direct mode is managed transparently by the TOraSession object, and you can easily return to connecting through OCI in Client mode at any time if restrictions above become critical for you.
