CN115686497A - Business development data management method, development engine, electronic device, and storage medium - Google Patents

Business development data management method, development engine, electronic device, and storage medium Download PDF

Info

Publication number
CN115686497A
CN115686497A CN202211415278.6A CN202211415278A CN115686497A CN 115686497 A CN115686497 A CN 115686497A CN 202211415278 A CN202211415278 A CN 202211415278A CN 115686497 A CN115686497 A CN 115686497A
Authority
CN
China
Prior art keywords
configuration information
model
domain model
instance
model instance
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
Application number
CN202211415278.6A
Other languages
Chinese (zh)
Inventor
范志强
马海银
王申
戴维豪
尚林纳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aisino Corp
Original Assignee
Aisino Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Aisino Corp filed Critical Aisino Corp
Priority to CN202211415278.6A priority Critical patent/CN115686497A/en
Publication of CN115686497A publication Critical patent/CN115686497A/en
Pending legal-status Critical Current

Links

Images

Abstract

The embodiment of the invention provides a business development data management method, a development engine, electronic equipment and a storage medium. The business development data management method comprises the following steps: obtaining a domain model example, wherein the domain model example comprises a plurality of block chain application business objects; determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects; obtaining database mapping configuration information associated with the field model instance in the metadata model, wherein the database mapping configuration information at least indicates a mapping relation between a block chain application field object and a business object data table of the field model instance; and storing the domain model instance into the business object data table through the data access configuration information.

Description

Business development data management method, development engine, electronic device, and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a business development data management method, a development engine, electronic equipment and a storage medium.
Background
With the rapid popularization of low-code development platforms, metadata technologies are rapidly developed and applied. The code rapid development platform realized based on the metadata engine can generally realize rapid development and delivery of applications, and has excellent performance in the aspects of interface code-free design, program automatic generation, rapid construction of data models and the like.
However, the strong coupling of the data model and the data operation causes that once the data model is changed, the data operation code needs to be rewritten, and the development efficiency is low.
Disclosure of Invention
In view of the above, embodiments of the present invention provide a business development data management method, a development engine, an electronic device, and a storage medium, so as to at least partially solve the above problems.
According to a first aspect of the embodiments of the present invention, there is provided a method for managing service development data, including: obtaining a domain model example, wherein the domain model example comprises a plurality of block chain application business objects; determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects; obtaining database mapping configuration information associated with the field model instance in the metadata model, wherein the database mapping configuration information at least indicates a mapping relation between a block chain application field object and a business object data table of the field model instance; and storing the domain model instance into the business object data table through the data access configuration information.
In another implementation manner of the present invention, the obtaining of the database mapping configuration information associated with the domain model instance in the metadata model includes: when the domain model instance is obtained, a model mapping interface is called based on the domain model instance, database mapping configuration information associated with the domain model instance is obtained, and the model mapping interface is configured with an association relation between the domain model instance and the metadata model.
In another implementation manner of the present invention, the storing the domain model instance in the business object data table includes: and storing the domain model instance into the business object data table through the data access interface, wherein the data access interface is configured with the association relationship between the metadata model association and the database mapping configuration information thereof.
In another implementation manner of the present invention, the storing the domain model instance in the business object data table through the data access configuration information includes: mapping configuration information through the database to generate a business object corresponding to the field model instance; and storing the business object in the business object data table.
In another implementation manner of the present invention, the obtaining of the database mapping configuration information associated with the metadata model includes: updating mapping configuration information of a database according to the changed service information in the field model example; associating the updated database mapping configuration information with the metadata model.
In another implementation of the invention, the method further comprises: determining a model instance identifier corresponding to the business object to be deleted based on the business type of the business object to be inquired; determining database mapping configuration information of the model instance identifier through the metadata model; and searching a target domain model instance corresponding to the model instance identification in the service object data table based on the database mapping configuration information to serve as the domain model instance where the service object to be inquired is located.
In another implementation manner of the present invention, the business object to be queried is deleted in the target domain model instance.
According to a second aspect of the embodiments of the present invention, there is provided a service development engine, including: the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module acquires a domain model example, and the domain model example comprises a plurality of block chain application service objects; the determining module is used for determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects; the second acquisition module is used for acquiring data access configuration information associated with the metadata model, wherein the data access configuration information indicates the mapping relation between the block chain application domain object of the domain model instance and the data table of the storage service object; and the storage module stores the domain model instance into the data table through the data access configuration information.
In another implementation manner of the present invention, the obtaining of the database mapping configuration information associated with the domain model instance in the metadata model includes: when the domain model instance is obtained, a model mapping interface is called based on the domain model instance, database mapping configuration information associated with the domain model instance is obtained, and the model mapping interface is configured with an association relation between the domain model instance and the metadata model.
In another implementation manner of the present invention, the storing the domain model instance in the business object data table includes: and storing the domain model instance into the business object data table through the data access interface, wherein the data access interface is configured with the association relationship between the metadata model association and the database mapping configuration information thereof.
In another implementation manner of the present invention, the storing the domain model instance into the business object data table by using the data access configuration information includes: mapping configuration information through the database to generate a business object corresponding to the field model instance; and storing the business object in the business object data table.
In another implementation manner of the present invention, the obtaining of the database mapping configuration information associated with the metadata model includes: updating mapping configuration information of a database according to the changed service information in the field model example; associating the updated database mapping configuration information with the metadata model.
In another implementation of the invention, the method further comprises: determining a model instance identifier corresponding to the business object to be deleted based on the business type of the business object to be inquired; determining database mapping configuration information of the model instance identifier through the metadata model; and searching a target domain model instance corresponding to the model instance identification in the service object data table based on the database mapping configuration information to serve as the domain model instance where the service object to be inquired is located.
In another implementation manner of the present invention, the business object to be queried is deleted in the target domain model instance.
According to a third aspect of embodiments of the present invention, there is provided an electronic apparatus, including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface are communicated with each other through the communication bus; the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the corresponding operation of the method according to the first aspect.
According to a fourth aspect of embodiments of the present invention, there is provided a computer storage medium having stored thereon a computer program which, when executed by a processor, performs the method of the first aspect.
In the scheme of the embodiment of the invention, the domain model examples comprise various block chain application service objects, the metadata model comprises attribute description of the various block chain service objects, the abstraction capability is improved, and the service development efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following descriptions are only some embodiments described in the embodiments of the present invention, and other drawings can be obtained by those skilled in the art according to these drawings.
FIG. 1 is a flow chart of steps of a method for managing business development data according to one embodiment of the present invention
FIG. 2 is a schematic flow diagram of the data management process of the embodiment of FIG. 1.
FIG. 3 is a schematic flow diagram of a data management process associated with the metadata model of the embodiment of FIG. 1.
Fig. 4 is a block diagram of a service development engine according to another embodiment of the present invention.
Fig. 5 is a schematic structural diagram of an electronic device according to another embodiment of the invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be described in detail below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention shall fall within the scope of the protection of the embodiments of the present invention.
In the conventional technology, the strong coupling of the data model and the data operation causes that once the data model is changed, the data operation code needs to be rewritten, and the development efficiency is low. For example, in the case that each Cell class attribute (referred to as attribute Vas) of a MetaModel is mapped to a corresponding table field, if a service changes, for example, a Vd object is added to the MetaModel lower list attribute vds, the corresponding table structure needs to be modified to add a new field for storage, which limits the rapid change of the service.
The following further describes specific implementation of the embodiments of the present invention with reference to the drawings.
FIG. 1 is a flow diagram of the steps of a method for business development data management, according to one embodiment of the invention. The service development data management method according to the embodiment of the present invention may be implemented by using a service development engine, where in this embodiment, the service development engine includes Vd, metaModel (a definition part of a metadata model), va, domain model (an instance part of a metadata model), cell object (an example of a blockchain application service object), and MetaModel dbmap (an example of database mapping configuration information).
Specifically, the business development data management method comprises the following steps:
s110: obtaining a domain model example, wherein the domain model example comprises a plurality of block chain application business objects.
It should be understood that S120: and determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects.
It should be understood that the metadata model covers data entities, data uplinks, data relationships; interface forms, interface views and interface charts; process definition and process instance; business logic; menus and the like. The instance portion of the metadata model is referred to as a Domainmodel, or class of Domainmodel. The instance values under each object of an instance DomainModel may be referred to as Cell objects (e.g., in the attribute List < Cell > cells of the DomainModel).
It should also be understood that the MetaModel in this context refers to the definition part of the metadata model, is a Java class, defines the object references of the MetaModel by the statement MetaModel = new MetaModel (), and creates a MetaModel object assigned to the object reference MetaModel. Note that MetaModel is a class and MetaModel is an object name. The MetaModel object is a different concept from the metaModel object, which generally refers to an object (reference) of a MetaModel class, and the metaModel object, which is a specific object (reference), whose object name is "MetaModel". Namely: and organizing a plurality of Vd objects in a logic unit to form a MetaModel.
In addition, vd is used to describe the data structure and first describes each attribute, and determines the code, name, text description, data type and uplink attribute information of each attribute. The va is used for storing the attribute value corresponding to each Vd object in the attribute List < Vd > vds under the MetaModel object.
It should also be understood that this step may be performed at the service layer.
S130: and acquiring database mapping configuration information associated with the field model instance in the metadata model, wherein the database mapping configuration information at least indicates a mapping relation between a block chain application field object and a business object data table of the field model instance.
It should be understood that this step may be performed at the data mapping layer (DM layer). Database mapping configuration information may be appended in the MetaModel for directing the DAO service to map Cell objects to database tables to include the domain model instances in the service object database table structure. The MetaModel describes the data structure and does not describe how to map cells to database tables, requiring the introduction of a database mapping configuration class, metaModelDbMap.
S140: and storing the domain model instance into the business object data table through the data access configuration information.
It should be understood that this step may be performed at the data access layer (DAO layer).
To sum up, the block chain rapid development framework of the business development engine can be composed of an MVC three-layer framework; m refers to a business model, V refers to a user interface, and C is a controller. The method of this embodiment uses MVC to implement code separation of M and V, and further puts a DM layer (data mapping layer) between the Service layer and the Service layer to implement separation of data model and data operation.
In the scheme of the embodiment of the invention, the domain model examples comprise various block chain application service objects, the metadata model comprises attribute description of the various block chain service objects, the abstraction capability is improved, and the service development efficiency is improved.
In other words, in the application development process, by using the metadata model, the related services of the domain model and the domain object can be unified only by defining two classes of the domain model (MetaModel) and the domain model instance (Domain model) without designing the class for each domain model, and the modification and implementation of the service interface are avoided, so that the flexibility of the domain model is improved.
It should be understood that the definition portion of the metadata model can be understood as a domain model (MetaModel), or a domain model (MetaModel) class, and the instance portion of the metadata model can be understood as a domain model instance (DomainModel), or a domain model instance (DomainModel) class.
FIG. 2 is a schematic flow diagram of the data management process of the embodiment of FIG. 1. When the method is called in the Service layer, preprocessing a Domain model (a domain model instance) in the Service, then transferring the Domain model serving as a parameter to the DM layer, further acquiring a corresponding MetaModel and MetaModelDbMap in the DM layer according to the Domain model, then persisting the Cell object, and traversing the Domain model of each child node of the Domain model. Then the corresponding Cell object is persisted, in other words, the persisted process can call the DAO layer, transmit the Cell and the MetaModeDbMap as parameters to the DAO, execute the database operation, and is compatible with the traditional DAO layer.
It should be understood that, the Service object and SQL are converted into each other in the DM layer, that is, in the case of not introducing the DM layer, SQL is visible to Service, and if the database system needs to be replaced, the logic of the Service layer and the DAO layer need to be modified at the same time, and decoupling between the two cannot be implemented. The DM layer of the embodiment of the invention can be used as a middle layer, and when modification is needed, only the DM layer and the DAO layer need to be modified, so that modification of the Service layer is avoided.
FIG. 3 is a schematic flow diagram of a data management process associated with the metadata model of the embodiment of FIG. 1. As shown in the figure, the metadata model aims at enabling services to change rapidly, and a data structure can change flexibly, so that the scheme of the embodiment of the invention can improve the flexibility of the structure design of the database table, and allows the dynamic expansion of the database when the MetaModel has new attributes, thereby avoiding the modification of the table structure. The reserved MetaModelDbMap can support the MetaModel to temporarily increase the Vd objects, and the corresponding Va objects can be saved in the T _ Va table on the premise of not modifying the table structure. Furthermore, a master table of CellTableName values can be configured for each MetaModel instance. Further, another extension table may also be configured by recording part of attribute values of the Cell object of the MetaModel in the extension table.
In other examples, the obtaining of the database mapping configuration information associated with the domain model instance in the metadata model includes: when the domain model instance is obtained, a model mapping interface is called based on the domain model instance, database mapping configuration information associated with the domain model instance is obtained, and the model mapping interface is configured with an association relation between the domain model instance and the metadata model. Because the model mapping interface is configured with the incidence relation between the field model instance and the metadata model, the storage of the business object database is realized through the database mapping configuration information. That is, the MetaModel describes the data structure and does not describe how to map the Cell to the database table, and the introduction of the database mapping configuration class, metaModelDbMap, is required. For example, the MetaModel dbmap can support the MetaModel to temporarily add the Vd object, and the corresponding Va object can be saved in the T _ Va table without modifying the table structure.
In other examples, the storing the domain model instance in the business object data table includes: and storing the domain model instance into the business object data table through the data access interface, wherein the data access interface is configured with the association relationship between the metadata model association and the database mapping configuration information thereof. And the mapping operation of the mapping configuration information of the database is realized through the data access interface, and the mapping operation is compatible to the data access interface.
In other examples, the storing the domain model instance in the business object data table via the data access configuration information includes: mapping configuration information through the database to generate a business object corresponding to the field model instance; and storing the business object in the business object data table.
In other examples, the obtaining of the database mapping configuration information associated with the metadata model includes: updating mapping configuration information of a database according to the changed service information in the field model example; associating the updated database mapping configuration information with the metadata model.
Specifically, firstly, incoming and participating domain models are preprocessed, metaModels are obtained according to businessType and MetaModelCode, and then each child node of the domain models is traversed, and the MetaModel is set for each domain model. And then, according to the MetaModelDbMap corresponding to the MetaModel, persisting the cells in the cells of the domain model object into a database.
In other examples, the method further comprises: determining a model instance identifier corresponding to the business object to be deleted based on the business type of the business object to be inquired; determining database mapping configuration information of the model instance identifier through the metadata model; and searching a target domain model instance corresponding to the model instance identification in the service object data table based on the database mapping configuration information to serve as the domain model instance where the service object to be inquired is located. The database mapping configuration information stores the target domain model, so that the searching efficiency of the business object to be inquired in the domain model is improved, and the table structure of the business object database does not need to be changed before and after the inquiry.
Specifically, first, the MetaModel of the instance is uniquely located by businessType and MetaModelCode. Then, calling a data mapping layer according to the MetaModel, acquiring an instance DomainModel, and searching a Cell object under the DomainModel according to the DomainModel. The user then returns a DomainModel object.
In other examples, the business object to be queried is deleted in the target domain model instance. Specifically, deletion may be based on a recursive process, that is, deletion is performed step by step from the last leaf in the domain model up to the instance corresponding to the parameter cellKey. The database mapping configuration information stores the target domain model, so that the deleting efficiency of the business object to be inquired in the domain model is improved, and the table structure of the business object database does not need to be changed before and after deletion.
Specifically, the parameter cellKey is a key value of an instance value, and is used to locate a MetaModel through the parameters businessType and MetaModel code, and then locates to a database mapping related configuration through the dbMapCode of the MetaModel, and then deletes the instance.
Fig. 4 is a block diagram of a service development engine according to another embodiment of the present invention. The business development engine of the embodiment comprises:
a first obtaining module 410, obtaining a domain model instance, where the domain model instance includes multiple block chain application service objects;
a determining module 420, configured to determine a metadata model to which the domain model instance belongs, where the metadata model includes attribute descriptions of the plurality of blockchain business objects;
a second obtaining module 430, configured to obtain data access configuration information associated with the metadata model, where the data access configuration information indicates a mapping relationship between a blockchain application domain object of the domain model instance and a data table storing a service object;
the storage module 440 stores the domain model instance in the data table according to the data access configuration information.
In the scheme of the embodiment of the invention, the domain model instance comprises a plurality of block chain application service objects, the metadata model comprises attribute descriptions of the plurality of block chain service objects, the abstraction capability is improved, the service development efficiency is improved, in addition, the database mapping configuration information at least indicates the mapping relation between the block chain application domain object of the domain model instance and the service object data table, the data access configuration information can store the domain model instance into the service object data table, and the decoupling of the service object and the service object data table in the domain model instance is realized.
In other examples, the obtaining of the database mapping configuration information associated with the domain model instance in the metadata model includes: when the domain model instance is obtained, a model mapping interface is called based on the domain model instance, database mapping configuration information associated with the domain model instance is obtained, and the model mapping interface is configured with an association relation between the domain model instance and the metadata model.
In other examples, the storing the domain model instance in the business object data table includes: and storing the domain model instance into the business object data table through the data access interface, wherein the data access interface is configured with the association relationship between the metadata model association and the database mapping configuration information thereof.
In other examples, the storing the domain model instance in the business object data table via the data access configuration information includes: mapping configuration information through the database to generate a business object corresponding to the field model instance; and storing the business object in the business object data table.
In other examples, the obtaining of database mapping configuration information associated with the metadata model includes: updating mapping configuration information of a database according to the changed service information in the field model example; associating the updated database mapping configuration information with the metadata model.
In other examples, the method further comprises: determining a model instance identifier corresponding to the business object to be deleted based on the business type of the business object to be inquired; determining database mapping configuration information of the model instance identifier through the metadata model; and searching a target domain model instance corresponding to the model instance identification in the service object data table based on the database mapping configuration information to serve as the domain model instance where the service object to be inquired is located.
In other examples, the business object to be queried is deleted in the target domain model instance.
The apparatus of this embodiment is used to implement the corresponding method in the foregoing method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again. In addition, the functional implementation of each module in the apparatus of this embodiment can refer to the description of the corresponding part in the foregoing method embodiment, and is not described herein again.
Referring to fig. 3, a schematic structural diagram of an electronic device according to another embodiment of the present invention is shown, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 3, the electronic device may include: a processor (processor) 302, a communication Interface (Communications Interface) 304, a memory (memory) 306 in which a program 310 is stored, and a communication bus 308.
The processor, the communication interface, and the memory communicate with each other via a communication bus.
And the communication interface is used for communicating with other electronic equipment or servers.
And the processor is used for executing the program, and particularly can execute the relevant steps in the method embodiment.
In particular, a program may include program code comprising at least one executable instruction.
The processor may be a processor CPU, or an Application Specific Integrated Circuit ASIC (Application Specific Integrated Circuit), or one or more Integrated circuits configured to implement embodiments of the present invention. The intelligent device comprises one or more processors which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And the memory is used for storing programs. The memory may comprise high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.
The program may specifically be configured to cause the processor to perform operations corresponding to the method of fig. 1: obtaining a domain model example, wherein the domain model example comprises a plurality of block chain application business objects; determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects; obtaining database mapping configuration information associated with the field model instance in the metadata model, wherein the database mapping configuration information at least indicates a mapping relation between a block chain application field object and a business object data table of the field model instance; and storing the domain model instance into the business object data table through the data access configuration information.
In addition, for specific implementation of each step in the program, reference may be made to corresponding steps and corresponding descriptions in units in the foregoing method embodiments, which are not described herein again. It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described devices and modules may refer to the corresponding process descriptions in the foregoing method embodiments, and are not described herein again.
It should be noted that, according to the implementation requirement, each component/step described in the embodiment of the present invention may be divided into more components/steps, and two or more components/steps or partial operations of the components/steps may also be combined into a new component/step to achieve the purpose of the embodiment of the present invention.
The above-described method according to an embodiment of the present invention may be implemented in hardware, firmware, or as software or computer code storable in a recording medium such as a CD ROM, a RAM, a floppy disk, a hard disk, or a magneto-optical disk, or as computer code originally stored in a remote recording medium or a non-transitory machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein may be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware such as an ASIC or FPGA. It is understood that a computer, processor, microprocessor controller, or programmable hardware includes memory components (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code that, when accessed and executed by a computer, processor, or hardware, implements the methods described herein. Further, when a general-purpose computer accesses code for implementing the methods illustrated herein, execution of the code transforms the general-purpose computer into a special-purpose computer for performing the methods illustrated herein.
Those of ordinary skill in the art will appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.
The above embodiments are only used for illustrating the embodiments of the present invention, and not for limiting the embodiments of the present invention, and those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of the present invention, so that all equivalent technical solutions also belong to the scope of the embodiments of the present invention, and the scope of patent protection of the embodiments of the present invention should be defined by the claims.

Claims (10)

1. A business development data management method includes:
obtaining a domain model example, wherein the domain model example comprises a plurality of block chain application business objects;
determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects;
obtaining database mapping configuration information associated with the domain model instance in the metadata model, wherein the database mapping configuration information at least indicates a mapping relation between a block chain application domain object and a business object data table of the domain model instance;
and storing the domain model instance into the business object data table through the data access configuration information.
2. The method of claim 1, wherein the obtaining database mapping configuration information associated with the domain model instance in the metadata model comprises:
when the domain model instance is obtained, a model mapping interface is called based on the domain model instance, database mapping configuration information associated with the domain model instance is obtained, and the model mapping interface is configured with an association relation between the domain model instance and the metadata model.
3. The method of claim 1, wherein the storing the domain model instance into the business object data table comprises:
and storing the domain model instance into the business object data table through the data access interface, wherein the data access interface is configured with the association relationship between the metadata model association and the database mapping configuration information thereof.
4. The method of claim 1, wherein said storing the domain model instance in the business object data table via the data access configuration information comprises:
mapping configuration information through the database to generate a business object corresponding to the field model instance;
and storing the business object in the business object data table.
5. The method of claim 4, wherein the obtaining database mapping configuration information associated with the metadata model comprises:
updating mapping configuration information of a database according to the changed service information in the field model example;
associating the updated database mapping configuration information with the metadata model.
6. The method of claim 1, wherein the method further comprises:
determining a model instance identifier corresponding to the business object to be deleted based on the business type of the business object to be inquired;
determining database mapping configuration information of the model instance identifier through the metadata model;
and searching a target domain model instance corresponding to the model instance identification in the service object data table based on the database mapping configuration information to serve as the domain model instance where the service object to be inquired is located.
7. The method of claim 5, wherein the business object to be queried is deleted in the target domain model instance.
8. A business development engine comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module acquires a domain model example which comprises a plurality of block chain application business objects;
the determining module is used for determining a metadata model to which the domain model instance belongs, wherein the metadata model comprises attribute descriptions of the various blockchain business objects;
a second obtaining module, configured to obtain data access configuration information associated with the metadata model, where the data access configuration information indicates a mapping relationship between a blockchain application domain object of the domain model instance and a data table storing business objects;
and the storage module stores the domain model instance into the data table through the data access configuration information.
9. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus; the memory is used for storing at least one executable instruction which causes the processor to execute the operation corresponding to the method as claimed in any one of claims 1-7.
10. A computer storage medium having stored thereon a computer program which, when executed by a processor, carries out the method of any one of claims 1-7.
CN202211415278.6A 2022-11-11 2022-11-11 Business development data management method, development engine, electronic device, and storage medium Pending CN115686497A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211415278.6A CN115686497A (en) 2022-11-11 2022-11-11 Business development data management method, development engine, electronic device, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211415278.6A CN115686497A (en) 2022-11-11 2022-11-11 Business development data management method, development engine, electronic device, and storage medium

Publications (1)

Publication Number Publication Date
CN115686497A true CN115686497A (en) 2023-02-03

Family

ID=85051202

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211415278.6A Pending CN115686497A (en) 2022-11-11 2022-11-11 Business development data management method, development engine, electronic device, and storage medium

Country Status (1)

Country Link
CN (1) CN115686497A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115993966A (en) * 2023-03-24 2023-04-21 美云智数科技有限公司 Application development system and method

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115993966A (en) * 2023-03-24 2023-04-21 美云智数科技有限公司 Application development system and method

Similar Documents

Publication Publication Date Title
CN105740411B (en) A kind of data migration method based on SOA and WebService
CN107038222B (en) Database cache implementation method and system
CN111881223B (en) Data management method, device, system and storage medium
CN109617646B (en) Message conversion method and device, computer equipment and computer readable storage medium
CN109087004B (en) Public workflow engine system based on domain model
CN109617647B (en) Message conversion method and device, computer equipment and computer readable storage medium
EP2178033A1 (en) Populating a multi-relational enterprise social network with disparate source data
CN104050276A (en) Cache processing method and system of distributed database
US8015195B2 (en) Modifying entry names in directory server
CN105447051A (en) Database operation method and device
CN105631019A (en) Metadata extension method and device
CN105843867A (en) Metadata model-based search method and search device based on metadata model
US9373093B2 (en) Gateway service manager for business object applications
CN108536617A (en) Buffer memory management method, medium, system and electronic equipment
CN111309868A (en) Knowledge graph construction and retrieval method and device
CN115686497A (en) Business development data management method, development engine, electronic device, and storage medium
CN101170436B (en) A method for managing template in network management system
CN104166705A (en) Access method and device of database
CN105468793A (en) Automated management method for simulation model data
CN102999329B (en) The Active Directory interface exploitation method of configuration is mapped based on extend markup language
US20090100082A1 (en) Replication and mapping mechanism for recreating memory durations
US20130297755A1 (en) Network element configuration management
CN1972276A (en) A management method and system for protocol access
CN117033454A (en) Data processing method, device, equipment and medium
US20220383219A1 (en) Access processing method, device, storage medium and program product

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