|
Server: Database: Help |
|
|
Select the class to display the properties associated. Each class can store its records into one or multiple Clusters (see "Structure" tab). A class can be schema-less (has no properties), schema-full (all properties as mandatories) or with a partial schema. | |
|
|
||
|
|
||
|
|
||
| Data segments are the segments that contain data pointed by Clusters. |
|
|
|
Clusters
are sets of records grouped by a mean. Any mean you want to assign. You can use a Cluster like a Table of the Relational DBMS world, namely to group records of the same type. Or you could want to group records by different logics.
There are two kinds of clusters: Physical and Logical. The first one uses ad-hoc files to speed up the I/O while the second one saves more space but it's slower. The suggestion is to use Physical Clusters for the records accessed often and where you need light speed. |
|
|
| Tx Segment handles the transaction log for the entire database. It's used in Transactions. |
|
|
|
|
|
|
|
|
|
| HTTP Method | Operation | Database | Argument(s) | |||
| / | http://localhost:2480/ | / | / | |||
|
||||||
| Below all the active connections. Keep in mind that HTTP connections are stateless, so no database is retained and usually after a short timeout (seconds) they are killed. Binary connections, instead, remain in life until the connection client closes it. Binary connections are used by the Orient Console tool and by any Orient Java applications that uses the native Java API. |
|
|
|
|
|
|
|
|
|
|
|
|
| Output: |