CLOB and ANYDATA support
Hello,
i have allready opened an SR 7467875.993 becoming an ER to this issue, but your support told me to type the same object into this Forum to ensure, that the problem will be faster handled. I am wondering about, but here I am:
I need the following issues with CLOB, ANYDATA and BINARY_DOUBLE.
1. ANYDATA shall be usable and implicitly castable in any function
2. ANYDATA & BINARY_DOUBLE shall be exportable and importable (via SqlDeveloper, export/import statement ...)
3. ANYDATA & CLOB shall be usable in any clause and comparison operator (not only like for CLOB = should work, too)
4. ANYDATA & CLOB functionality shall be implemented at least as much as it is for NUMBER, CHAR or VARCHAR2.
5. ANYDATA & CLOB shall be supported on indices (everything can be represented as a string (see MS-.Net object member functions).
6. ANYDATA & CLOB shall be possible to use in multiple columns of a single row.
7. sys.anydata.convertCLOB(clob) shall be assignable to a value of a anydata column in a table via an update sql statement.
8. Even a CLOB, NUMBER, ..... object shall be assignable to a vale of a anydata column without any explicit convertion function required.
9. ANYDATA shall be converted implicitely into the value its represents in all functions.
I ask for this, because I think as a typed data storage system any datatype storable in that system shall be completely supported without any limitations. Escpecially without logical inconsitencies.
Regards,
Dirk