CN109359116A - A kind of storage method and equipment of entity relationship - Google Patents
A kind of storage method and equipment of entity relationship Download PDFInfo
- Publication number
- CN109359116A CN109359116A CN201811591633.9A CN201811591633A CN109359116A CN 109359116 A CN109359116 A CN 109359116A CN 201811591633 A CN201811591633 A CN 201811591633A CN 109359116 A CN109359116 A CN 109359116A
- Authority
- CN
- China
- Prior art keywords
- entity
- relationship
- pointer
- attribute
- storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to a kind of storage methods of entity relationship, comprising the following steps: creation entity storage unit, storage entity and entity information;Based on entity information, creation is for the entity secondary index database by condition query entity;Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship;The present invention can hold the storage of a large amount of entity and relationship, and can support easily to retrieve, such as retrieved according to entity name, entity attribute, relation name, facilitate and excavate associated entity.
Description
Technical field
The present invention relates to a kind of storage method of entity relationship and equipment, belong to database technical field.
Background technique
Entity relationship is a kind of universal presence, the common relationship as between enterprise and its client, company key personnel
With the relationship of enterprise, relationship is quite useful data for scenes such as such as financial air controls.This entity relationship in existing situation
Storage be based primarily upon common relevant database mode: such as by between enterprise A, enterprise B, enterprise A and enterprise B relationship store
It is recorded at one, forms a triple.There are multiple relationships between entity, then just storing a plurality of record.However it will lead in this way
When inquiring, managing and maintaining, one layer of relationship of such as enterprise A and two layers of relationship could be looked by needing to do a complicated inquiry
Inquiry comes out.
With big data technology development and application like a raging fire, a bigger relational graph urgently establishes concurrent real body
Between useful incidence relation, as data volume increases, once be related to high concurrent access or addition, delete and modification etc. close
Tethers operation, not only the efficiency of relation chain operation is very low, but also it is difficult to ensure that data consistency.
Summary of the invention
In order to solve above-mentioned problems of the prior art, the present invention provides a kind of storage method of storage relationship, with
It supports the storage of a large amount of entity and relationship, and can support easily to retrieve, such as according to entity name, entity attribute, relationship name
Title etc. is retrieved, and is facilitated and is excavated associated entity.
Technical scheme is as follows:
Technical solution one
A kind of storage method of entity relationship, comprising the following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship.
Further, the creation relationship storage unit, is created by the way of doubly linked list, the specific steps are as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database.
Further, the creation entity storage, is created using the method for key-value distributed storage;It is described
Entity information includes the mode bit of entity, first relationship of entity and entity attribute inventory;
The wherein mode bit of the entity, the state for mark-up entity;
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute;The entity attribute inventory is written independent
Database forms the entity secondary index database.
Technical solution two
A kind of equipment of entity relationship storage, including memory and processor, the memory are stored with instruction, and described instruction is suitable
In being loaded by processor and execute following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship.
Further, the creation relationship storage unit, is created by the way of doubly linked list, the specific steps are as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database.
Further, the creation entity storage, is created using the method for key-value distributed storage;It is described
Entity information includes the mode bit of entity, first relationship of entity and entity attribute inventory;
The wherein mode bit of the entity, the state for mark-up entity;
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute;The entity attribute inventory is written independent
Database forms the entity secondary index database.
The invention has the following beneficial effects:
1, a kind of storage method of entity relationship of the present invention establishes entity two by being based on entity information and attribute of a relation inventory
Grade index data base and relationship secondary index database can carry out entity and relationship according to entity information and attribute of a relation
Condition query.
2, relationship is stored by way of doubly linked list, using the entity at relationship both ends as the node in doubly linked list,
When inquiry, the preamble node and postorder node of entity can be very easily inquired, that is, the previous entity of entity and latter
Entity.
3, storage entity, first relationship of entity and entity attribute inventory, inquiry velocity by way of key-value
Fastly, store data volume is big, supports high concurrent;To provide basis for incidence relation excavation.
Detailed description of the invention
Fig. 1 is the effect picture of the embodiment of the present invention;
Fig. 2 is the schematic diagram that the embodiment of the present invention creates entity storage unit;
Fig. 3 is the schematic diagram that the embodiment of the present invention creates relationship storage unit;
Fig. 4 is the flow chart that the embodiment of the present invention creates relationship.
Specific embodiment
It is next in the following with reference to the drawings and specific embodiments that the present invention will be described in detail.
Embodiment one
Referring to Fig. 1-3, a kind of storage method of entity relationship, comprising the following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship, attribute of a relation is clear
It is single, the field including indicating attribute of a relation, than as shown in figure 1, the attribute 3 and attribute 5 of relationship 1.
The present embodiment establishes entity secondary index database and relationship two by being based on entity information and attribute of a relation inventory
Grade index data base, can inquire entity and relationship according to entity information and attribute of a relation.
Embodiment two
Referring specifically to Fig. 4, further, the creation relationship storage unit is created, specific steps by the way of doubly linked list
It is as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database;Below with Fig. 1 and
The creation of relationship storage unit is explained for Fig. 3:
In Fig. 1, the relationship occurred in order is followed successively by relationship 1, relationship 2 and relationship 3, and the relationship between entity A and entity B is to close
It is 1, the relationship between entity A and entity C is relationship 2, and the relationship between entity B and entity C is relationship 3;
In newly-increased relationship 1, store the entity A and entity B at 1 both ends of relationship, then respectively the preamble of storage entity A and entity B and
Subsequent pointer.
In the relationship 1 of write-in, because being the relationship of first appearance, entity A and entity B are in entity storage unit without phase
Entity relationship is closed, so newly-built relationship A and relationship B and be written in entity storage unit, and by the entity A and entity B in relationship 1
Preamble pointer and subsequent pointer be directed toward it is empty.
When relationship 2 is written, it is related to two entities of entity A and entity C, entity A has existed in entity storage unit,
So the preamble pointer of entity A has been directed toward the preamble pointer of the A in relationship 1 in relationship 2, while updating original is the entity A in 1
Subsequent pointer be directed toward the subsequent pointer position of entity A in relationship 2, and in relationship 2 the subsequent pointer of entity A be directed toward it is empty, newly
Entity C is built, and the preamble pointer of the entity C in relationship 2 and subsequent pointer are directed toward sky;When newly-increased relationship 3,3 both ends of relationship
In entity B and the existing entity storage unit of entity C, so by real in the preamble pointer points relationship 1 of entity B in relationship 3
The preamble pointer of body B, in more new relation 1 in the postorder pointer points relationship 3 of entity B entity B postorder pointer, will be in relationship 3
The preamble pointer of entity C in the preamble pointer points relationship 2 of entity C, the postorder pointer points relationship 3 of entity C in more new relation 2
The postorder pointer of middle entity C, and the postorder pointer of entity B and entity C are directed to sky in relationship 3.
Referring specifically to Fig. 2, further, creation entity storage, using key-value distributed storage method into
Row creation;The entity information include entity mode bit (because entity be it is deletable, mode bit be used to presentation-entity whether
Be deleted), first relationship of entity and entity attribute inventory;
The wherein mode bit of the entity, for mark-up entity state (because entity be it is deletable, mode bit be used to indicate
Whether entity is deleted);
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute, example as shown in figure 1, the attribute 1 and attribute of entity A
2;Independent database is written into the entity attribute inventory, forms the entity secondary index database.
The present embodiment not only has the beneficial effect of embodiment one, it is further proposed that, by way of doubly linked list
Storage relationship, in inquiry, can very easily inquire entity using the entity at relationship both ends as the node in doubly linked list
Preamble node and postorder node, that is, the previous entity and latter entity of entity;
Storage entity, first relationship of entity and entity attribute inventory by way of key-value, inquiry velocity is fast, deposits
Put that data volume is big, supports high concurrent.
Embodiment three
Referring to Fig. 1-3, a kind of equipment of entity relationship storage, including memory and processor, the memory are stored with instruction,
Described instruction is suitable for being loaded by processor and executing following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship, attribute of a relation is clear
It is single, the field including indicating attribute of a relation, than as shown in figure 1, the attribute 3 and attribute 5 of relationship 1.
The present embodiment establishes entity secondary index database and relationship two by being based on entity information and attribute of a relation inventory
Grade index data base, can inquire entity and relationship according to entity information and attribute of a relation.
Example IV
Referring specifically to Fig. 4, further, the creation relationship storage unit is created, specific steps by the way of doubly linked list
It is as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database;Below with Fig. 1 and
The creation of relationship storage unit is explained for Fig. 3:
In Fig. 1, the relationship occurred in order is followed successively by relationship 1, relationship 2 and relationship 3, and the relationship between entity A and entity B is to close
It is 1, the relationship between entity A and entity C is relationship 2, and the relationship between entity B and entity C is relationship 3;
In newly-increased relationship 1, store the entity A and entity B at 1 both ends of relationship, then respectively the preamble of storage entity A and entity B and
Subsequent pointer.
In the relationship 1 of write-in, because being the relationship of first appearance, entity A and entity B are in entity storage unit without phase
Entity relationship is closed, so newly-built relationship A and relationship B and be written in entity storage unit, and by the entity A and entity B in relationship 1
Preamble pointer and subsequent pointer be directed toward it is empty.
When relationship 2 is written, it is related to two entities of entity A and entity C, entity A has existed in entity storage unit,
So the preamble pointer of entity A has been directed toward the preamble pointer of the A in relationship 1 in relationship 2, while updating original is the entity A in 1
Subsequent pointer be directed toward the subsequent pointer position of entity A in relationship 2, and in relationship 2 the subsequent pointer of entity A be directed toward it is empty, newly
Entity C is built, and the preamble pointer of the entity C in relationship 2 and subsequent pointer are directed toward sky;When newly-increased relationship 3,3 both ends of relationship
In entity B and the existing entity storage unit of entity C, so by real in the preamble pointer points relationship 1 of entity B in relationship 3
The preamble pointer of body B, in more new relation 1 in the postorder pointer points relationship 3 of entity B entity B postorder pointer, will be in relationship 3
The preamble pointer of entity C in the preamble pointer points relationship 2 of entity C, the postorder pointer points relationship 3 of entity C in more new relation 2
The postorder pointer of middle entity C, and the postorder pointer of entity B and entity C are directed to sky in relationship 3.
Referring specifically to Fig. 2, further, creation entity storage, using key-value distributed storage method into
Row creation;The entity information includes the mode bit of entity, first relationship of entity and entity attribute inventory;
The wherein mode bit of the entity, for mark-up entity state (because entity be it is deletable, mode bit be used to indicate
Whether entity is deleted);
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute, example as shown in figure 1, the attribute 1 and attribute of entity A
2;Independent database is written into the entity attribute inventory, forms the entity secondary index database.
The present embodiment not only has the beneficial effect of embodiment three, it is further proposed that, by way of doubly linked list
Storage relationship, in inquiry, can very easily inquire entity using the entity at relationship both ends as the node in doubly linked list
Preamble node and postorder node, that is, the previous entity and latter entity of entity;
Storage entity, first relationship of entity and entity attribute inventory by way of key-value, inquiry velocity is fast, deposits
Put that data volume is big, supports high concurrent;It is stored with the relationship of first generation of entity, because of the storage Two-way Chain tabular form of relationship
, by first relationship, n-th second relationship, third relationship ... of relationship of entity can be inquired;
Entity secondary index database and relationship secondary index database are clear based on entity attribute inventory and attribute of a relation respectively
It singly establishes, in inquiry, condition query can be carried out by input entity or the attribute of relationship.
The above description is only an embodiment of the present invention, is not intended to limit the scope of the invention, all to utilize this hair
Equivalent structure or equivalent flow shift made by bright specification and accompanying drawing content is applied directly or indirectly in other relevant skills
Art field, is included within the scope of the present invention.
Claims (6)
1. a kind of storage method of entity relationship, which comprises the following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship.
2. a kind of storage method of entity relationship according to claim 1, it is characterised in that: the creation relationship storage is single
Member is created by the way of doubly linked list, the specific steps are as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database.
3. a kind of storage method of entity relationship according to claim 2, it is characterised in that: the creation entity storage,
It is created using the method for key-value distributed storage;The entity information include the mode bit of entity, entity first
A relationship and entity attribute inventory;
The wherein mode bit of the entity, the state for mark-up entity;
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute;The entity attribute inventory is written independent
Database forms the entity secondary index database.
4. a kind of equipment of entity relationship storage, which is characterized in that including memory and processor, the memory is stored with finger
It enables, described instruction is suitable for being loaded by processor and executing following steps:
Create entity storage unit, storage entity and entity information;
Based on entity information, creation is for the entity secondary index database by condition query entity;
Creation relationship storage unit stores the entity and attribute of a relation inventory of relationship, relationship both ends;
Based on attribute of a relation inventory, create for the relationship secondary index database by condition query relationship.
5. a kind of storage equipment of entity relationship according to claim 4, it is characterised in that: the creation relationship storage is single
Member is created by the way of doubly linked list, the specific steps are as follows:
Newly-increased relationship request is initiated, judges whether the entity at newly-increased relationship both ends is already present in entity storage unit;
If at least one is not present in entity storage unit the entity at newly-increased relationship both ends, entity is created, storage is worked as
The preceding entity and entity information being not present;Newly-built entity finishes, into newly-built relationship step;
If the entity at newly-increased relationship both ends exists in entity storage unit, it is directly entered newly-built relationship step;
Newly-built relationship, is written the entity and attribute of a relation inventory at relationship both ends, and defining relationship both ends is the knot in doubly linked list
Point, and the preamble pointer and subsequent pointer of two entities are stored respectively;If any entity at current relation both ends is present in relationship
In storage unit, then the preamble pointer of the entity is directed toward to the preamble pointer of previous entity, and by the postorder pointer of previous entity
It is directed toward the postorder pointer of current entity;If any entity at current relation both ends is not present in relationship storage unit, should
The preamble pointer and postorder pointer of entity are directed to sky;
Independent database is written into the attribute of a relation inventory, forms the relationship secondary index database.
6. a kind of storage equipment of entity relationship according to claim 5, it is characterised in that: the creation entity storage,
It is created using the method for key-value distributed storage;The entity information include the mode bit of entity, entity first
A relationship and entity attribute inventory;
The wherein mode bit of the entity, the state for mark-up entity;
Wherein first relationship of the entity, for the relationship of entity first generation;
The wherein entity attribute inventory, the field including presentation-entity attribute;The entity attribute inventory is written independent
Database forms the entity secondary index database.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811591633.9A CN109359116A (en) | 2018-12-20 | 2018-12-20 | A kind of storage method and equipment of entity relationship |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811591633.9A CN109359116A (en) | 2018-12-20 | 2018-12-20 | A kind of storage method and equipment of entity relationship |
Publications (1)
Publication Number | Publication Date |
---|---|
CN109359116A true CN109359116A (en) | 2019-02-19 |
Family
ID=65329406
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201811591633.9A Pending CN109359116A (en) | 2018-12-20 | 2018-12-20 | A kind of storage method and equipment of entity relationship |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN109359116A (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1407487A (en) * | 2001-08-03 | 2003-04-02 | 奥弗图尔服务公司 | System and method for providing location and price protection in searching list generated by computer network searching engine |
US6986102B1 (en) * | 2000-01-21 | 2006-01-10 | International Business Machines Corporation | Method and configurable model for storing hierarchical data in a non-hierarchical data repository |
US9031998B2 (en) * | 2008-12-30 | 2015-05-12 | Sap Se | Analytics enablement objects |
CN106802947A (en) * | 2017-01-13 | 2017-06-06 | 中国工商银行股份有限公司 | The data handling system and method for entity relationship diagram |
-
2018
- 2018-12-20 CN CN201811591633.9A patent/CN109359116A/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6986102B1 (en) * | 2000-01-21 | 2006-01-10 | International Business Machines Corporation | Method and configurable model for storing hierarchical data in a non-hierarchical data repository |
CN1407487A (en) * | 2001-08-03 | 2003-04-02 | 奥弗图尔服务公司 | System and method for providing location and price protection in searching list generated by computer network searching engine |
US9031998B2 (en) * | 2008-12-30 | 2015-05-12 | Sap Se | Analytics enablement objects |
CN106802947A (en) * | 2017-01-13 | 2017-06-06 | 中国工商银行股份有限公司 | The data handling system and method for entity relationship diagram |
Non-Patent Citations (3)
Title |
---|
TAUQEER HUSSAIN 等: "An Effort-Based Approach to Measure Completeness of an Entity-Relationship Model", 《 SEVENTH IEEE/ACIS INTERNATIONAL CONFERENCE ON COMPUTER AND INFORMATION SCIENCE (ICIS 2008)》 * |
王书海 等: "一种采用双向有序链表存储的动态编码位图索引方法", 《石家庄铁道大学学报(自然科学版)》 * |
达微: "Neo4j图数据库简介和底层原理", 《HTTPS://WWW.JIANSHU.COM/P/7BD33AB83B71》 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9002802B2 (en) | High throughput, reliable replication of transformed data in information systems | |
JP4195444B2 (en) | Method and system for extending file system APIs | |
US7289973B2 (en) | Graphical user interface for system and method for managing content | |
JP5710851B2 (en) | System and method for impact analysis | |
CN1329858C (en) | Dynamic data manipulation system based on object format and its method | |
US9672241B2 (en) | Representing an outlier value in a non-nullable column as null in metadata | |
US20020062301A1 (en) | System for providing extended file attributes | |
US20130218843A1 (en) | Intelligent data archiving | |
US7958167B2 (en) | Integration of unstructed data into a database | |
CA2379930A1 (en) | Multi-model access to data | |
CN101334785A (en) | Method for organizing dummy catalog and managing naming space for distributed file systems | |
US20110113319A1 (en) | Introducing a form instance into an information container | |
US6606631B1 (en) | IMS on-line reorganization utility | |
CN107092685A (en) | A kind of method that file system and RDBMS store transaction data are used in combination | |
US20120185451A1 (en) | Data processing method and system for database management system | |
US7181473B1 (en) | Identifying files within a namespace | |
CN109359116A (en) | A kind of storage method and equipment of entity relationship | |
US11803450B2 (en) | Creating a tree of database states | |
CN114489829B (en) | Remote sensing image sample labeling method based on ArcMap | |
US20220197885A1 (en) | Hybrid shadow paging for storing a database | |
KR102214697B1 (en) | A computer program for providing space managrment for data storage in a database management system | |
CN110008188B (en) | External storage quota system of application software at file system level | |
US8706769B1 (en) | Processing insert with normalize statements | |
CN110245148A (en) | A kind of date storage method, device, system and medium | |
CN109760044A (en) | A kind of data processing method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |