Oracle JSON Relational Duality delivers a capability that provides the benefits of both relational tables and JSON documents, without the trade-offs of either approach.
A simple example like this uses data stored in multiple normalized relational tables: a student table, a teacher table, a course table, and a table mapping students to their courses. But it is not always straightforward for developers, even in a simple example like this, to build the course schedule for one student.
What if we could use JSON syntax to express table instances interchangeably with SQL statements, while still storing data efficiently in relational tables?
[
add
]
[
|
|
...
]