CN112948395A

CN112948395A - Data processing method and device for database and computer readable medium

Info

Publication number: CN112948395A
Application number: CN202110335013.4A
Authority: CN
Inventors: 杨涛; 张亚军; 陈诚; 王红奇
Original assignee: Zhejiang Taimei Medical Technology Co Ltd
Current assignee: Zhejiang Taimei Medical Technology Co Ltd
Priority date: 2021-03-29
Filing date: 2021-03-29
Publication date: 2021-06-11
Anticipated expiration: 2041-03-29
Also published as: CN112948395B

Abstract

The invention relates to a data processing method for a database, which comprises the following steps: editing program elements in an application program, wherein the program elements correspond to tables in a database; creating a first annotation of the program element, the first annotation including current table description information of the table corresponding to the program element; starting the application program to acquire the original table description information of the database; comparing the description information of the current table with the description information of the original table to obtain the description information of a newly added table which is different from the description information of the original table in the description information of the current table; and creating a new table in the database, wherein the new table corresponds to the description information of the new table. According to the invention, the mapping between the program elements and the tables in the database can be automatically realized, the error report of the program caused by the fact that the program elements and the database are not mapped in time is avoided, and the development time is saved.

Description

Data processing method and device for database and computer readable medium

Technical Field

The present invention relates to the field of database technologies, and in particular, to a data processing method and apparatus for a database, and a computer readable medium.

Background

In the internet era, object-oriented technologies cover almost all software design, application, and engineering fields. Meanwhile, relational databases such as Oracle, DB2 and SQLServer occupy most of the database fields. When a relational database is used as a data storage mode of an object-oriented technology application, the object-oriented technology and the database technology are required to be cooperated with each other.

Object Mapping relationships (ORMs) are objects in an Object oriented language program that can be automatically persisted into a relational database using metadata that describes the Mapping between the objects and the database. The technical scheme has the advantages that the data are objectified, developers can directly develop object entities in the logic objects without considering the content of the data tables, the relation among the data tables and the like, and the framework can perform corresponding processing when the objects are subjected to persistent processing. Schema is the organization and structure of a database, and Schema objects may include tables (tables), columns (columns), data types (data types), relationships (relationships), and the like.

At present, when a subject entity changes, the change needs to be mapped into a Schema architecture of a database artificially, and a mapping relation exists between a subject and the Schema architecture of the database. When the object entity is frequently changed, the programmer often forgets to perform the mapping step of Schema in the database, resulting in error reporting due to mismatch between the entity object and the database structure at program startup. Moreover, the current mapping method is low in efficiency, and time cost of project development is increased.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a data processing method and a data processing device for a database, wherein the data processing method and the data processing device are used for automatically mapping objects and a database architecture.

The technical solution adopted by the present invention to solve the above technical problems is a data processing method for a database, comprising: editing program elements in an application program, wherein the program elements correspond to tables in a database; creating a first annotation of the program element, the first annotation including current table description information of the table corresponding to the program element; starting the application program to acquire the original table description information of the database; comparing the description information of the current table with the description information of the original table to obtain the description information of a newly added table which is different from the description information of the original table in the description information of the current table; and creating a new table in the database, wherein the new table corresponds to the description information of the new table.

In an embodiment of the present invention, the step of editing the program element in the application program includes: creating a new program element, wherein the new program element corresponds to a new table in the database; and/or changing at least one item of information in the table description information of the table corresponding to the program element.

In an embodiment of the present invention, before starting the application program, the method further includes: creating a second annotation in a launcher of the application, the second annotation comprising a command to perform a scan of a path in which the program element is located.

In an embodiment of the present invention, the path includes a path in which an upper-level program element of the program elements is located.

In an embodiment of the present invention, the step of starting the application further includes: and obtaining starting parameters, wherein the starting parameters comprise data source information of the database, and the data source information at least comprises a connection address and a port number of the database.

In an embodiment of the present invention, the current table description information at least includes a table name.

In an embodiment of the invention, the program elements comprise Java objects.

In an embodiment of the invention, said first annotation is a JPA annotation.

The present invention further provides a data processing apparatus for a database to solve the above technical problem, comprising: a memory for storing instructions executable by the processor; a processor for executing the instructions to implement the method as described above.

The present invention also provides a computer readable medium storing computer program code, which when executed by a processor implements the method as described above.

The invention can obtain the description information of the newly added table by creating the first annotation for the program element and comparing the description information of the current table in the first annotation with the description information of the original table in the database, thereby automatically creating a new table corresponding to the description information of the newly added table in the database. According to the invention, the mapping between the program elements and the tables in the database can be automatically realized, the error report of the program caused by the fact that the program elements and the database are not mapped in time is avoided, and the development time is saved.

Drawings

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below, wherein:

FIG. 1 is an exemplary flow chart of a software object and database structure mapping method;

FIG. 2 is an exemplary flow chart of a data processing method for a database in accordance with an embodiment of the present invention;

fig. 3 is a system block diagram of a data processing apparatus for a database according to an embodiment of the present invention.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways than those specifically described herein, and thus the present invention is not limited to the specific embodiments disclosed below.

As used in this application and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise. Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description. Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate. In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

It should be noted that the terms "first", "second", and the like are used to define the components, and are only used for convenience of distinguishing the corresponding components, and the terms have no special meanings unless otherwise stated, and therefore, the scope of protection of the present application is not to be construed as being limited. Further, although the terms used in the present application are selected from publicly known and used terms, some of the terms mentioned in the specification of the present application may be selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Further, it is required that the present application is understood not only by the actual terms used but also by the meaning of each term lying within.

Flow charts are used herein to illustrate operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.

FIG. 1 is an exemplary flow chart of a software object and database structure mapping method. Referring to fig. 1, the mapping method includes the following steps:

step S110: adding an object in the software;

step S120: newly adding a table in a database;

step S130: the software project is started.

The software in step S110 refers to an object oriented program, and the object refers to an object in the object oriented program, where the object corresponds to a table in the database, and the attribute of the object corresponds to the attribute of the table. The programmer may change the settings of the objects in the software, such as adding new objects. Since the object is added in step S110, the programmer needs to manually add a table in the database in step S120, the added table corresponding to the added object in step S110. Step S120 may also be accomplished by a programmer using some tool.

After steps S110 and S120 are completed, the item of software is started in step S130. Since the mapping relationship between the software object and the table in the database structure has been completed in steps S110 and S120, the software project can be smoothly started in step S130 without error.

However, according to the embodiment shown in fig. 1, whether a programmer manually adds tables to a database or a tool is used to operate the database, there are problems of inefficiency and error-susceptibility. In practical applications, the programmer only executes step S110 and forgets to execute step S120, and after the software project is started, an error is reported, which hinders software development.

Fig. 2 is an exemplary flowchart of a data processing method for a database according to an embodiment of the present invention. Referring to fig. 2, the data processing method of this embodiment includes the steps of:

step S210: editing program elements in the application program, wherein the program elements correspond to tables in the database;

step S220: creating a first annotation of the program element, wherein the first annotation comprises current table description information of a table corresponding to the program element;

step S230: starting an application program, and acquiring original table description information of a database;

step S240: comparing the description information of the current table with the description information of the original table to obtain the description information of a newly added table which is different from the description information of the original table in the description information of the current table; and

step S250: and creating a new table in the database, wherein the new table corresponds to the description information of the new table.

The respective steps of this example are explained in detail below.

In step S210, the present invention does not limit the application program therein, and preferably, the application program is a data collection and management program used in the clinical trial process.

The program element in step S210 refers to an operation object of the programmer at the time of developing the application. In a preferred embodiment, the application employs object-oriented techniques, with program elements referring to packages, classes, objects, fields, methods, local variables, method parameters, etc., defined by a programmer in an object-oriented language, the program elements corresponding to tables in a database. The invention does not limit the specific attribute and quantity of the table in the database corresponding to the program element.

The present invention does not limit the number of program elements in step S210. In step S210, one or more program elements may be edited, and each program element may correspond to a table in the database.

In some embodiments, the program element is a Java object. Accordingly, an application refers to a Java program or Java software Project (Project).

In some embodiments, the specific implementation of step S210 includes, but is not limited to, the following two methods:

step S211: creating a new program element, wherein the new program element corresponds to a new table in the database;

step S212: and changing at least one item of information in the table description information of the table corresponding to the program element.

Step S211 and step S212 may be executed alternatively or simultaneously.

In performing step S211, a new program element is created, which corresponds to a new table in the database, with table name B. The new table here means that the original database does not have the table having the table name B.

The table description information of the table in the database includes a plurality of items of information, such as table names, indexes, column names, column attributes, and the like. In step S212, at least one item of information in the table description information is changed, and assuming that the table name in the table description information of the table is changed and the table name of the table corresponding to the program element is originally a, the table name is changed to B in step S212.

In some embodiments, multiple program elements may be edited, for example, step S211 is performed on a first program element, that is, a new first program element is created, where the first program element corresponds to a new table in the database, and the table name is B; step S212 is executed for the second program element, the table name of the table corresponding to the second program element is changed, and the original table name a is modified to a new table name C. Then in a subsequent step, after the comparison of step S240, new tables B and C are created simultaneously in step S250.

In some embodiments, multiple items of information in the table description information of the table corresponding to the program element may be changed at the same time in step S212.

In step S220, a first annotation is created for the program element in step S210.

The first annotation may be written by a programmer including current table description information for the table to which the program element corresponds. It is understood that tables in the database are used for storing data, and the tables usually have information of table names, indexes, column names, attributes of the columns, and the like, wherein the table names are suitable for representing the names of the tables different from other tables; the index is adapted to quickly point to data in the table; the column name is adapted to represent the name of a column in the table; the attributes of a column are adapted to indicate the type of data stored in the column, such as character, numeric value, text, etc., and may further include information such as field length, etc. These pieces of information may be included in the table description information of the table.

In some embodiments, the first annotation is a JPA annotation, indicating that the first annotation complies with the standards of JPA. JPA is short for Java Persistence API and is an object Persistence specification. JPA annotation is the use of annotations to implement JPA-related configuration work. In a preferred embodiment, the application program may refer to a Java program implemented in Java programming language, and the JPA annotation is a code level metadata that can be declared in front of program elements such as packets, class files, fields, methods, local variables, method parameters, etc. to explain and comment on the program elements, etc. Annotations may be considered as an interface through which a program may obtain annotations specifying program elements and obtain information about the program elements with which the annotations are associated, and may be used by developers to track dependencies in source code or to check code when performing basic compilation, etc.

In the embodiment of the present invention, the first annotation on the program element edited in step S210 may prompt the possible changes of these program element objects and their corresponding objects in the database.

In step S230, the original table description information of the database may be automatically obtained when the application is started. The database in step S230 has not established a new mapping relationship with the program element edited in step S210. Referring to the previous example, assuming that the database originally includes a table with a table name a, the original table description information includes the table description information of table a.

In some embodiments, the step of launching the application further comprises: and obtaining starting parameters, wherein the starting parameters comprise data source information of the database, and the data source information at least comprises a connection address and a port number of the database.

In these embodiments, the step of obtaining the startup parameters may set the corresponding command by the application. According to the starting parameter, when the application program is started, the application program can access the database through the connection address and the port number of the database, so as to obtain the related information of the database, wherein the related information at least comprises the original table description information of the table.

When an application corresponds to multiple databases, the startup parameters may specify which database the application is to be started on.

In some embodiments, before starting the application program, the method further comprises: a second annotation is created in the launcher of the application, the second annotation comprising a command to perform a scan of the path in which the program element is located. From this second annotation, the program element edited in step S220 and its first annotation may be scanned.

In some embodiments, the path in the second annotation comprises a path in which an upper level program element of the program element is located. In embodiments where the program elements are Java objects, the application includes a start-up Class (Class). For Java programs, a start Class refers to a Class (Class) that needs to be loaded when a Java program item starts. The second annotation may be configured on the launch class, the second annotation including a command to execute a path on which the Java object is scanned. A Package (Package) is a program element that is one level higher than a class, that is, a Package is an upper level program element of a class, and similarly, a class is an upper level program element of an object. Therefore, the path of the packet in which the start class is located is included in the second annotation, and the application program scans the packet path to obtain the Java object created in step S220 and the first annotation thereof.

In some embodiments, the second annotation is the @ dblnspect () annotation.

In some embodiments, the second annotation is not a JPA annotation.

In some embodiments, the second annotation is a custom annotation.

In some embodiments, prior to launching the application, the data processing method of the present invention provides a user interface on which the user can edit the second annotation.

In other embodiments, after the application is started, the program elements in all paths are automatically scanned, and the first annotation of the Java object created in step S220 can be obtained.

In step S240, the current table description information and the original table description information are compared, and the addition table description information different from the original table description information in the current table description information is obtained. Continuing with the previous example, if a new Java object is created in step S210, which corresponds to a new table with table name B, the new table description information is the description information of the new table B after step S240. If the table name of the table corresponding to the original Java object is changed in step S210, and the original table name a is changed to table name C, the description information of the new table is the description information of the new table C. The present invention does not limit whether other information of the new table C is changed, such as column attribute information. It will be appreciated that the table name of the new table C has changed, and that the columns and column attributes in the table may be the same as or different from those in Table A. The specific structure of the new table may be included in the first annotation.

In step S250, a new table corresponding to the description information of the new addition table may be automatically created in the database based on the description information of the new addition table obtained in step S240. That is, a new table is created in the database based on the new table description information. For example, if the table name in the added table description information is B, the table name of the new table is B. Of course, other contents of the new table, such as columns, column attributes, etc., may also be created according to the description information of the new table.

Through steps S210-S250, automatic mapping from program elements in the application to tables in the database is completed. When a program element in an application program is edited, particularly a new program element corresponding to a new table is created, or table description information of a table corresponding to the program element is changed, the corresponding new table can be automatically created in the database. Therefore, program error report caused by the fact that the database is not mapped with the program elements in time can be avoided, and development time is saved.

The invention also includes a data processing apparatus for a database comprising a memory and a processor. Wherein the memory is to store instructions executable by the processor; the processor is configured to execute the instructions to implement the data processing method for the database as described above.

Fig. 3 is a system block diagram of a data processing apparatus for a database according to an embodiment of the present invention. Referring to fig. 3, the data processing apparatus 300 may include an internal communication bus 301, a processor 302, a Read Only Memory (ROM)303, a Random Access Memory (RAM)304, and a communication port 305. When applied to a personal computer, the data processing apparatus 300 may further include a hard disk 307. An internal communication bus 301 may enable data communication among the components of the data processing apparatus 300. Processor 302 may make the determination and issue a prompt. In some embodiments, processor 302 may be comprised of one or more processors. The communication port 305 can enable data communication of the data processing apparatus 300 with the outside. In some embodiments, the data processing device 300 may send and receive information and data from a network through the communication port 305. The data processing apparatus 300 may also comprise various forms of program storage units and data storage units, such as a hard disk 307, a Read Only Memory (ROM)303 and a Random Access Memory (RAM)304, capable of storing various data files for computer processing and/or communication, and possibly program instructions for execution by the processor 302. The processor executes these instructions to implement the main parts of the method. The results processed by the processor are communicated to the user device through the communication port and displayed on the user interface.

The data processing method can be implemented as a computer program, stored in the hard disk 307, and loaded into the processor 302 for execution, so as to implement the data processing method of the present application.

The invention also comprises a computer-readable medium having stored thereon computer program code which, when executed by a processor, implements the data processing method for a database as described hereinbefore.

When the data processing method for the database is implemented as a computer program, it may also be stored in a computer-readable storage medium as an article of manufacture. For example, computer-readable storage media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD)), smart cards, and flash memory devices (e.g., electrically Erasable Programmable Read Only Memory (EPROM), card, stick, key drive). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media (and/or storage media) capable of storing, containing, and/or carrying code and/or instructions and/or data.

It should be understood that the above-described embodiments are illustrative only. The embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processor may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and/or other electronic units designed to perform the functions described herein, or a combination thereof.

Aspects of the present application may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present application may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).

The computer readable medium may comprise a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, and the like, or any suitable combination. The computer readable medium can be any computer readable medium that can communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device. Program code on a computer readable medium may be propagated over any suitable medium, including radio, electrical cable, fiber optic cable, radio frequency signals, or the like, or any combination of the preceding.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing disclosure is by way of example only, and is not intended to limit the present application. Various modifications, improvements and adaptations to the present application may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present application and thus fall within the spirit and scope of the exemplary embodiments of the present application.

Also, this application uses specific language to describe embodiments of the application. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the present application is included in at least one embodiment of the present application. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the present application may be combined as appropriate.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

Claims

1. A data processing method for a database, comprising:

editing program elements in an application program, wherein the program elements correspond to tables in a database;

creating a first annotation of the program element, the first annotation including current table description information of the table corresponding to the program element;

starting the application program to acquire the original table description information of the database;

comparing the description information of the current table with the description information of the original table to obtain the description information of a newly added table which is different from the description information of the original table in the description information of the current table; and

and creating a new table in the database, wherein the new table corresponds to the description information of the new table.

2. The data processing method of claim 1, wherein the step of editing the program element in the application program comprises: creating a new program element, the new program element corresponding to the new table in the database; and/or changing at least one item of information in the table description information of the table corresponding to the program element.

3. The data processing method of claim 1, further comprising, prior to launching the application: creating a second annotation in a launcher of the application, the second annotation comprising a command to perform a scan of a path in which the program element is located.

4. A data processing method according to claim 3, wherein said path includes a path in which an upper-level program element of said program elements is located.

5. The data processing method of claim 1, wherein the step of launching the application further comprises: and obtaining starting parameters, wherein the starting parameters comprise data source information of the database, and the data source information at least comprises a connection address and a port number of the database.

6. The data processing method of claim 1, wherein the current table description information includes at least a table name.

7. A data processing method according to claim 1, wherein said program element comprises a Java object.

8. The data processing method of claim 7, wherein the first annotation is a JPA annotation.

9. A data processing apparatus for a database, comprising:

a memory for storing instructions executable by the processor;

a processor for executing the instructions to implement the method of any one of claims 1-8.

10. A computer-readable medium having stored thereon computer program code which, when executed by a processor, implements the method of any of claims 1-8.