Hello, everyone.
How are you doing?
As I said in the last post, Oracle JSON-Relational Duality Views bring the best of both worlds - JSON and Relational.
But everything in the Database World has restrictions. And Duality Views are not different.
If you want to check out all the restrictions in the manual, click on the image below.
Column data types:
TIMESTAMP WITH LOCAL TIME ZONE
BINARY_DOUBLE
BFILE
ROWID / UROWID
XMLTYPE
ANYTYPE
ANYDATA
ANYDATASET
HTTPURIType / XDBURIType / DBURIType
SDO_POINT_TYPE
SDO_ELEM_INFO_ARRAY
SDO_ORDINATE_ARRAY
SDO_GEOMETRY
SDO_TOPO_GEOMETRY
Object types (Abstract Data Types)
BINARY_DOUBLE
BFILE
ROWID / UROWID
XMLTYPE
ANYTYPE
ANYDATA
ANYDATASET
HTTPURIType / XDBURIType / DBURIType
SDO_POINT_TYPE
SDO_ELEM_INFO_ARRAY
SDO_ORDINATE_ARRAY
SDO_GEOMETRY
SDO_TOPO_GEOMETRY
Object types (Abstract Data Types)
They cannot be used to create Duality Views:
System-partitioned tables
Sharded tables
Views
Materialized views
Editioning views
External tables
Hybrid partitioned tables
Global temporary tables
Private temporary tables
Remote tables (tables over database links)
Sharded tables
Views
Materialized views
Editioning views
External tables
Hybrid partitioned tables
Global temporary tables
Private temporary tables
Remote tables (tables over database links)
Other restrictions:
Duality Views updates using database links are not supported.
MERGE SQL statements are not supported.
It is not possible to create a JSON functional index on a data column.
It is not possible to create a JSON multivalue index on a data column.
It does not have support for JSON search index on subjacent table column.
Fine-grained auditing policies are not supported.
We still have 15 more restrictions, according to the manual.
That's it! I hope this post helps you!
Regards
Mario
Nenhum comentário:
Postar um comentário
Isso te ajudou? Comente...