I learned about Oracle Table Partitioning and object-relational database system.
1. oracle partitioning
Oracle partitions are introduced in oracle 8.0. This process physically breaks down a table or index into smaller and more manageable parts. In terms of database access, logically, there is only one table or one index, but physically this table or index may consist of dozens of physical partitions, each of which is an independent object, it can be processed independently or as part of a larger object.
2. Benefits of partitioning
2.1 improve data availability
2.2 Removing large segments from the database (breaking them down into small segments) reduces the management burden.
2.3 improve the performance of some queries
2.4 The modification can be distributed to multiple separate partitions to reduce competition on the large-capacity OLTP system.
3. Table Partitioning
Common Table Partitioning methods:
3.1 interval Partition
3.2 hash partitions
3.3 list partitions
3.4 combined partitioning
Object-based databases provide methods like processing class c ++, inheritance, so that we can handle problems that do not meet the first paradigm (all attributes have atomicity.
We can define a type like a class, and inherit and expand it to get the data structure that we can understand in reality, it can also be expressed and stored in the database.
Arrays and multiple collections are also mentioned here.
We can operate arrays (SQL-1999) in the database, just as we define and operate in c ++.
This SQL feature is implemented in oracle.
Multi-set (SQL-2003) is actually a single set of nesting, a bit similar, multi-dimension group, set nested set.
Of course, the object reference is provided in the object-oriented programming language. an attribute of type in SQL can be a reference to an object of the specified type.
References are a little complicated, so I won't say much about them.