CN112965723B - Object database implementation method and virtual object database - Google Patents
Object database implementation method and virtual object database Download PDFInfo
- Publication number
- CN112965723B CN112965723B CN202110365244.XA CN202110365244A CN112965723B CN 112965723 B CN112965723 B CN 112965723B CN 202110365244 A CN202110365244 A CN 202110365244A CN 112965723 B CN112965723 B CN 112965723B
- Authority
- CN
- China
- Prior art keywords
- database
- virtual object
- atomic
- definition
- access request
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/447—Target code generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/235—Update request formulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the disclosure provides an object database implementation method and a virtual object database, belonging to the technical field of data processing, and specifically comprising the following steps: establishing a virtual object database, wherein the virtual object database is used for packaging an original database and uniformly converting different original database services into object database services; when a new original database is accessed, mapping the atomic entity structure to the virtual object database to form an atomic object definition; according to the incidence relation of the atomic entities, the atomic object is defined, expanded and assembled to construct and form a virtual object definition; compiling the access request according to the virtual object definition to generate an execution code; and operating the execution code to access the original database and outputting a target data set corresponding to the access request. According to the scheme disclosed by the invention, the traditional database is packaged into the object database, so that the object query method is provided, and the convenience and the development efficiency of data processing are improved.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of data processing, in particular to an object database implementation method and a virtual object database.
Background
Traditional object database implementations employ fixed object structures to physically store data objects. In practical application, the data association relationship is complex and changeable, such as: the order can be a child node of the user object, and the user can also be a child node of the order object; such a variable association may result in a large amount of data being stored repeatedly, and the conventional object database is rarely practically used in business practice.
And the traditional relational database data logic and business logic are tightly coupled, the development is complex and difficult to maintain, the self-service data development capability of a front-end business user is greatly limited, and the tuning difficulty of a data platform is increased.
Therefore, a simple and efficient object database implementation method is needed.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide an object database implementation method, which at least partially solves the problems in the prior art that the development process is complex and difficult to maintain.
In a first aspect, an embodiment of the present disclosure provides an object database implementation method, including:
establishing a virtual object database, wherein the virtual object database is used for packaging an original database and uniformly converting different original database services into object database services;
when a new original database is accessed, mapping the atomic entity structure to the virtual object database to form an atomic object definition;
according to the incidence relation of the atomic entities, constructing and generating a virtual object definition by defining, expanding and assembling the atomic object;
when receiving an access request for a virtual object in the virtual object database, compiling the access request according to the definition of the virtual object to generate an execution code;
and operating the execution code to access the original database, and outputting a target data set corresponding to the access request.
According to a specific implementation manner of the embodiment of the present disclosure, the step of mapping the atomic entity structure to the virtual object database when accessing a new original database to form an atomic object definition includes:
and reading the data structure of the original entity in the original database, and mapping the data structure in the virtual object database to form the atomic object definition by combining data source information.
According to a specific implementation manner of the embodiment of the present disclosure, the step of constructing and forming the virtual object definition by defining, expanding and assembling the atomic object definition according to the association relationship of the atomic entity includes:
and according to the definition and the incidence relation of the atomic entity, defining expansion on the basis of the atomic object, assembling the multi-level nested child objects of the object, and forming a complete virtual object definition in the virtual object database.
According to a specific implementation manner of the embodiment of the present disclosure, when receiving an access request for a virtual object in the virtual object database, compiling the access request according to the virtual object definition to generate an execution code, includes:
and compiling the access request according to the type of the original database by combining the mapping of the primitive entity in the virtual object according to the definition of the virtual object, and generating an execution code adapted to the original database.
According to a specific implementation manner of the embodiment of the present disclosure, the step of running the execution code to access the original database and outputting the target data set corresponding to the access request includes:
and according to the type of the original database corresponding to the access request virtual object, the code is adaptively executed on the corresponding original database and a corresponding target data set is output.
According to a specific implementation manner of the embodiment of the present disclosure, the operation language of the virtual object database is an object query language.
In a second aspect, an embodiment of the present disclosure provides a virtual object database, configured to implement the object database implementation method provided in the foregoing disclosure, where the virtual object database includes:
the mapping module is used for mapping the atomic entity structure to the virtual object database to form an atomic object definition;
the object definition module is used for defining and expanding on the basis of the atomic object according to the definition and the incidence relation of the atomic entity, assembling multi-level sub-objects of the object and forming a complete virtual object in a virtual object database;
an input module for receiving an access request for a virtual object;
the compiling module is used for compiling the access request received by the input module according to the virtual object definition to generate an execution code;
the execution module is used for operating the execution code to access the original database and obtaining a target data set corresponding to the access request;
and the output module is used for outputting the target data set corresponding to the access request.
The object database implementation method in the embodiment of the disclosure includes: establishing a virtual object database, wherein the virtual object database is used for packaging an original database and uniformly converting different original database services into object database services; when a new original database is accessed, mapping the atomic entity structure to the virtual object database to form an atomic object definition; according to the incidence relation of the atomic entities, the atomic object is defined, expanded and assembled to construct and form a virtual object definition; when receiving an access request for a virtual object in the virtual object database, compiling the access request according to the definition of the virtual object to generate an execution code; and operating the execution code to access the original database, and outputting a target data set corresponding to the access request. According to the scheme, the traditional database is packaged into the object database in a virtual object mode, the data logic is packaged into the virtual object, the data logic and the service logic in the database are separated, a target query method is provided for a user, and convenience and development efficiency of data processing are greatly improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of an object database implementation method according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a virtual object structure involved in an object database implementation method according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of a data access flow involved in an object database implementation method according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram illustrating a principle of converting a conventional relational database SQL into a virtual object database OSQL according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a virtual object database provided in the embodiment of the present disclosure.
Detailed Description
The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
Before explaining the embodiments of the present disclosure in detail, some key terms related to the embodiments of the present disclosure are explained.
The protocarpous body: the atomic entity is an entity table of physical storage source data, and may also be a data set such as a file and a message, for example: customer, order, etc.
Atomic object: an atomic object is a mapping of atomic entity data structure definitions in a virtual object database, including atomic entity structure definitions and atomic entity network association paths.
Virtual object: the virtual data object is a tree-like level nested data structure view, each data object corresponds to a main atomic entity, and the granularity of the object is determined by the main atomic entities. The object contains several nested children, which can nest them. Virtual objects store only the definition of the object structure and the mapping to the atomic entity, and do not physically store object data.
OSQL: the invention defines an object structured query language which is used for defining or processing and accessing data in an object mode and is divided into an object data definition language and an object data operation language.
ODDL: object data definition language, part of OSQL language for generating atomic object definitions and generating virtual object definitions.
ODML: the object data operation language, the part for accessing the object in the OSQL language, can perform the operations of adding and deleting, modifying and checking the object or the nodes in the object.
The embodiments of the present disclosure are described below with specific examples, and other advantages and effects of the present disclosure will be readily apparent to those skilled in the art from the disclosure in the specification. It is to be understood that the described embodiments are merely illustrative of some, and not restrictive, of the embodiments of the disclosure. The disclosure may be embodied or carried out in various other specific embodiments, and various modifications and changes may be made in the details within the description without departing from the spirit of the disclosure. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present disclosure, and the drawings only show the components related to the present disclosure rather than the number, shape and size of the components in actual implementation, and the type, amount and ratio of the components in actual implementation may be changed arbitrarily, and the layout of the components may be more complicated.
In addition, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects may be practiced without these specific details.
The embodiment of the present disclosure provides an object database implementation method, a flow of the method is shown in fig. 1, and the method includes steps S101 to S105:
referring to fig. 1, a schematic flowchart of a virtual object database implementation method provided in the embodiment of the present disclosure is shown. As shown in fig. 1, the method mainly comprises the following steps:
s101, establishing a virtual object database, wherein the virtual object database is used for packaging an original database and uniformly converting different original database services into object database services;
in specific implementation, the traditional object database is considered to adopt a fixed object structure, data objects are physically stored, for complex and changeable data association relations, a large amount of data can be repeatedly stored, and the data are rarely used practically in business practice; and the traditional relational database data logic and business logic are tightly coupled, the development is complex and difficult to maintain, the self-service data development capability of a front-end business user is greatly limited, and the tuning difficulty of a data platform is increased.
The virtual object database may be built, which may store only definitions of object relational structures and mappings to the atomic entities in the original database. Of course, the original database may be a traditional relational database, or may be an emerging NOSQL or NewSQL database, or the like.
S102, when a new original database is accessed, mapping an atomic entity structure to the virtual object database to form an atomic object definition;
in practical implementation, if the original database may contain a plurality of atomic entities, the atomic entity structure may be mapped to the virtual object database to form a plurality of atomic object definitions; the atomic object definition stores not only the data structure of the corresponding atomic entity but also the network association path of the atomic entity.
S103, according to the incidence relation of the atomic entities, constructing and generating a virtual object definition by expanding and assembling the atomic object definition;
when the method is specifically implemented, a needed atomic object is selected as a root object of a virtual data object, then the incidence relation between the needed atomic object and a sub-object is defined, and for large-scale complex incidence needing performance optimization, a user can define an execution path of the sub-object incidence. Considering that there are multiple atomic entities in the primary database and the associations between different atomic entities, for example, an order form may include a list of items and an order payment form, which may be a sub-form belonging to a customer table, the object association logic between all objects in the virtual object database may be determined and the complete virtual object may be generated according to the object association logic.
The definition of the virtual object comprises original database information, original entity, field information and the incidence relation between the atomic entities, and a standardized data acquisition program can be generated based on the information, and corresponding grammar adaptation is required for each data source.
It should be noted that the computationally derived attributes may also be extended based on the original attributes of the virtual object, and these computationally derived attributes may also be used within the organization. Unlike traditional SQL, which places entity associations on various scattered SQL code segments, virtual data objects can be reused within enterprises and organizations. It should be noted that the object association logic may also be determined according to actual requirements, and different association logics may be determined according to multiple requirements. If the virtual object to be accessed is a user, the structure of the virtual object is shown in fig. 2.
S104, when receiving an access request for a virtual object in the virtual object database, compiling the access request according to the definition of the virtual object to generate an execution code;
when an access request for a virtual object in the virtual object database is received, the access request can be analyzed and processed, and a virtual object structural relationship which needs to be accessed by the access request is extracted. Generating corresponding data access codes of source tables, messages and files according to the original data definition mapped by the virtual object definition to be accessed, generating data organization codes according to the incidence relation among corresponding original entities, generating data processing/access codes according to an OSQL script developed by a service user, and finally generating complete codes by combining the codes. Considering that the access request may access different types of databases, the access request may be adapted according to the type of database and compiled to generate the executable code. Such as MR procedures Batch, Spark-Streaming procedures, Spark-Batch procedures, Flink Streaming procedures, Storm Streaming procedures, SQL scripts, etc.
And S105, operating the execution code to access the original database, and outputting a target data set corresponding to the access request.
After the execution code is generated, the execution code may be executed to access the original database and then output a target data set corresponding to the access request.
According to the virtual object database implementation method provided by the embodiment of the disclosure, the access request is compiled, the execution code is generated, and the execution code is run to access the entity data in the original database, so that different access requests can be processed uniformly, and convenience and development efficiency of data processing are improved.
On the basis of the above embodiment, as described in step S102, when accessing a new original database, mapping an atomic entity structure to the virtual object database to form an atomic object definition, including:
and reading the data structure of the original entity in the original database, and mapping the data structure in the virtual object database to form the atomic object definition by combining data source information.
In specific implementation, when a new original database is accessed, the data structure of the original entity in the original database may be read, and the atomic object definition is mapped and formed in the virtual object database in combination with data source information.
Optionally, in step S103, the step of constructing and forming a virtual object definition by defining, expanding and assembling the atomic object definition according to the association relationship of the atomic entities includes:
and according to the definition and the incidence relation of the atomic entity, defining expansion on the basis of the atomic object, assembling the multi-level nested child objects of the object, and forming a complete virtual object definition in the virtual object database.
For example, according to the definitions and association relations of all the atomic entities in the original database, extension may be defined on the basis of atomic objects, and multiple levels of nested child objects of objects may be assembled to form a complete virtual object definition in the virtual object database.
On the basis of the foregoing embodiment, when receiving an access request for a virtual object in the virtual object database, the compiling the access request according to the virtual object definition to generate an execution code in step S104 includes:
and compiling the access request according to the type of the original database by combining the mapping of the primitive entity in the virtual object according to the definition of the virtual object, and generating an execution code adapted to the original database.
In specific implementation, when an access request for a virtual object in the virtual object database is received, the access request may be compiled according to the type of the original database by combining with the mapping of the primitive entity in the virtual object according to the definition of the virtual object, so as to generate an execution code adapted to the original database.
On the basis of the foregoing embodiment, in step S105, executing the execution code to access the original database, and outputting the target data set corresponding to the access request includes:
and according to the type of the original database corresponding to the access request virtual object, the code is adaptively executed on the corresponding original database and a corresponding target data set is output.
In specific implementation, after the execution code is generated, the execution code may be run, and the code is adaptively executed on a corresponding original database according to the original database type corresponding to the access request virtual object, and a corresponding target data set is output.
Optionally, the operation language of the virtual object database is an object query language.
In specific implementation, the operation language of the virtual object database is an object structured query language OSQL, the language for generating the atomic object definition and generating the virtual object definition is an object data definition language ODDL, and the language for accessing the object is an object data operation language ODML.
Referring to fig. 3, a schematic diagram of a data access flow of a virtual object database implementation method provided in the embodiment of the present disclosure is shown.
301 issues data queries or data processing requests to virtual data objects in the virtual object database using the OSQL language for the user.
The OSQL is an object structure query language, and realizes the decoupling of business logic and data logic through the decomposition of the traditional SQL.
In the traditional SQL syntax, each SQL statement includes a select clause and a from + where + group clause, the select clause describes business logic, the from + where + group clause describes data association logic and aggregation logic, and the execution performance of the SQL statement is generally determined by the from and the where clauses. Each SQL statement comprises data logic and business logic, and the data logic and the business logic are tightly coupled.
In OSQL, the from + where + group section is abstracted away to define common data objects, defined by ODDL, which can be generally responsible for definition and maintenance by the data platform technology role in enterprises and organizations. The business logic expression in the select clause is extracted and defined by ODML, self-service definition of business users is supported, users with biased business only need to pay attention to the business logic, data association logic (association fields, association modes, execution optimization and the like) does not need to be known, the business logic is decoupled from the data logic, front-end development complexity is simplified, and complexity generated by code compiling is also simplified.
The principle of OSQL implementing the decoupled separation of business logic and data logic compared to traditional SQL is shown in fig. 4.
In specific implementation, when a user requests to access virtual object data by using the OSQL based on the virtual object definition, the service logic expression of the virtual object may be used, taking the client object shown in fig. 2 as an example:
number of orders of customer: order, count of customer
Customer order amount (null value taken to be 0): customer, order, sum (0)
Customer who purchased the mobile phone goods:
if { customer, order, filter (item detail item type ═ cell phone "). count >0} {" yes "} else {" no "}
The access request is compiled and forwarded to the original database by the virtual object database 302 according to the definition of the virtual object, and the original database can be a traditional relational database, and can also be a Nosql or Newsql database.
303 is to execute the compiled program on the original database and return the execution result/result set to the virtual object database.
304 the virtual object database returns the result to the user side corresponding to the request.
Corresponding to the above method embodiment, referring to fig. 5, the disclosed embodiment further provides a virtual object database 50, including:
an input module 501, configured to receive an access request for a virtual object;
a mapping module 502, configured to map an atomic entity structure to the virtual object database to form an atomic object definition;
an object definition module 503, configured to define and expand on the basis of the atomic object according to the definition and association relationship of the atomic entity, assemble multiple levels of sub-objects of the object, and form a complete virtual object in the virtual object database;
a compiling module 504, configured to compile the access request received by the input module according to the virtual object definition, and generate an execution code;
an executing module 505, configured to run the executing code to access the original database, and obtain a target data set corresponding to the access request;
an output module 506, configured to output the target data set corresponding to the access request.
The apparatus shown in fig. 5 may correspondingly execute the content in the above method embodiment, and details of the part not described in detail in this embodiment refer to the content described in the above method embodiment, which is not described again here.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware.
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof.
The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.
Claims (5)
1. An object database implementation method, comprising:
establishing a virtual object database, wherein the virtual object database is used for packaging an original database and uniformly converting different original database services into object database services;
when a new original database is accessed, mapping the atomic entity structure to the virtual object database to form an atomic object definition;
according to the incidence relation of the atomic entities, the atomic object is defined, expanded and assembled to construct and form a virtual object definition;
when receiving an access request for a virtual object in the virtual object database, compiling the access request according to the definition of the virtual object to generate an execution code;
running the execution code to access the original database, and outputting a target data set corresponding to the access request;
wherein, the operation language of the virtual object database is an object query language;
the step of constructing and forming the virtual object definition by defining, expanding and assembling the atomic object according to the incidence relation of the atomic entities comprises the following steps:
and according to the definition and the incidence relation of the atomic entity, defining expansion on the basis of the atomic object, assembling the multi-level nested child objects of the object, and forming a complete virtual object definition in the virtual object database.
2. The method of claim 1, wherein the step of mapping the atomic entity structure to the virtual object database when accessing the new original database to form an atomic object definition comprises:
and reading the data structure of the original entity in the original database, and mapping the data structure in the virtual object database to form the atomic object definition by combining data source information.
3. The method of claim 1, wherein the step of compiling the access request to generate execution code according to the virtual object definition when receiving the access request to the virtual object in the virtual object database comprises:
and compiling the access request according to the type of the original database by combining the mapping of the primitive entity in the virtual object according to the definition of the virtual object, and generating an execution code adapted to the original database.
4. The method of claim 1, wherein the step of executing the executable code to access the original database and output the target data set corresponding to the access request comprises:
and according to the type of the original database corresponding to the access request virtual object, the code is adaptively executed on the corresponding original database and a corresponding target data set is output.
5. An object database implementation apparatus, configured to implement the object database implementation method according to any one of claims 1 to 4, the object database implementation apparatus comprising:
the mapping module is used for mapping the atomic entity structure to the virtual object database to form an atomic object definition;
the object definition module is used for defining and expanding on the basis of the atomic object according to the definition and the incidence relation of the atomic entity, assembling multi-level sub-objects of the object and forming a complete virtual object in a virtual object database;
an input module for receiving an access request for a virtual object;
the compiling module is used for compiling the access request received by the input module according to the virtual object definition to generate an execution code;
the execution module is used for operating the execution code to access the original database and obtaining a target data set corresponding to the access request;
and the output module is used for outputting the target data set corresponding to the access request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110365244.XA CN112965723B (en) | 2021-04-01 | 2021-04-01 | Object database implementation method and virtual object database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110365244.XA CN112965723B (en) | 2021-04-01 | 2021-04-01 | Object database implementation method and virtual object database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112965723A CN112965723A (en) | 2021-06-15 |
| CN112965723B true CN112965723B (en) | 2021-12-28 |
Family
ID=76281130
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110365244.XA Active CN112965723B (en) | 2021-04-01 | 2021-04-01 | Object database implementation method and virtual object database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112965723B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462559A (en) * | 2014-12-25 | 2015-03-25 | 广东电子工业研究院有限公司 | Mainstream relation type database table mode objectification and virtualization mechanism |
| CN107220259A (en) * | 2016-03-22 | 2017-09-29 | 北京京东尚科信息技术有限公司 | A kind of database extension system, equipment and the method for extending database |
| CN107491510A (en) * | 2017-08-03 | 2017-12-19 | 国网江苏省电力公司信息通信分公司 | One kind mixing heterogeneous data source unified query system and distributed enquiring method |
| CN108984620A (en) * | 2018-06-14 | 2018-12-11 | 中国科学院重庆绿色智能技术研究院 | A kind of relevant database and its design method of dynamic scalable |
| CN111209319A (en) * | 2018-11-21 | 2020-05-29 | 华为技术有限公司 | Data service method and device |
-
2021
- 2021-04-01 CN CN202110365244.XA patent/CN112965723B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462559A (en) * | 2014-12-25 | 2015-03-25 | 广东电子工业研究院有限公司 | Mainstream relation type database table mode objectification and virtualization mechanism |
| CN107220259A (en) * | 2016-03-22 | 2017-09-29 | 北京京东尚科信息技术有限公司 | A kind of database extension system, equipment and the method for extending database |
| CN107491510A (en) * | 2017-08-03 | 2017-12-19 | 国网江苏省电力公司信息通信分公司 | One kind mixing heterogeneous data source unified query system and distributed enquiring method |
| CN108984620A (en) * | 2018-06-14 | 2018-12-11 | 中国科学院重庆绿色智能技术研究院 | A kind of relevant database and its design method of dynamic scalable |
| CN111209319A (en) * | 2018-11-21 | 2020-05-29 | 华为技术有限公司 | Data service method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112965723A (en) | 2021-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2877943B1 (en) | Mapping entities in data models | |
| Simitsis et al. | State-space optimization of ETL workflows | |
| JP6488317B2 (en) | Mapping of attributes of keyed entities | |
| de la Vega et al. | Mortadelo: Automatic generation of NoSQL stores from platform-independent data models | |
| US20190005092A1 (en) | Query optimization using propagated data distinctness | |
| US8209340B2 (en) | Efficient functional representation of result shaping | |
| EP3293644B1 (en) | Loading data for iterative evaluation through simd registers | |
| CN116795859A (en) | Data analysis method, device, computer equipment and storage medium | |
| EP3293645B1 (en) | Iterative evaluation of data through simd processor registers | |
| Koupil et al. | A universal approach for multi-model schema inference | |
| KR20130064160A (en) | System of entity-relationship model reformulation of sparql query results on rdf data and the method | |
| Sroka et al. | Translating relational queries into spreadsheets | |
| CN118043798A (en) | Data aggregation in a hierarchy for query execution | |
| Sridhar et al. | RAPID: Enabling scalable ad-hoc analytics on the semantic web | |
| US10521431B2 (en) | Relational conversion of multiprovider operations in a calculation scenario for executing a query | |
| CN112965723B (en) | Object database implementation method and virtual object database | |
| Azzam et al. | Towards making distributed rdf processing flinker | |
| Alaoui et al. | Semantic Oriented Data Modeling for Enterprise Application Engineering Using Semantic Web Languages | |
| Schildgen et al. | Transformations on Graph Databases for Polyglot Persistence with NotaQL | |
| US12038921B2 (en) | Transforming operations of a computer program for execution at a database | |
| Hawkins et al. | An introduction to data representation synthesis | |
| Pivert | NoSQL Data Models | |
| Träris et al. | Where the Path Leads: State of the Art and Challenges of Graph Database Systems | |
| Sampaio et al. | Query processing in DOQL: A deductive database language for the ODMG model | |
| Fang et al. | RDF Date Storage Scheme Based on Graph Database |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |