CN102110111A - Method and system for processing database operating command - Google Patents

Abstract

The invention discloses a processing method and device for database operation commands. Wherein, the method includes: encapsulating the database operation command; calling the encapsulated database operation command. Through the present invention, the processing of the operation command to the database can be realized simply.

Description

Method and device for processing database operation commands

technical field

The present invention relates to the field of computer technology, in particular to a method and device for processing database operation commands.

Background technique

The invention relates to the encapsulation of the processing method of database data commands, provides developers with a general database operation method, ensures the reusability and unity of data layer operations, and thus ensures the stability of the system.

In the process of project development, the differences in programming styles of the project team development members and the flexibility of database operation statement SQL have brought more and more difficulties in operation and maintenance to the project team. For example: to fetch all the data from the user table, some people will write it as select*fromuser; some people will write it as select all from user; some people will write it as Select Name (all fields) from user.

Although there will be no errors in the operation, it will have a bad feeling when others read the program, and redundant code will be generated. If this program difference is many orders of magnitude in the project, then in During the development process, the program will appear in various styles, and the difficulty of maintenance is greatly increased.

At present, Hibernate is the most widely used for database operation encapsulation. The advantages and disadvantages are as follows. The advantages include: abandoning the idea of the database center, complete object-oriented thinking, no need for database knowledge, and low entry barriers for project members; the disadvantages include: it is difficult to control under a large number of multi-table and complex queries, and requires a deep foundation; debugging is difficult, It is not easy to get started; the mapping is complicated, and the integration environment is more troublesome.

Aiming at the problem that the operation of the database is relatively complicated in the related art, no effective solution has been proposed yet.

Contents of the invention

The present invention is proposed to solve the problem of complex database operations in the related art. Therefore, the main purpose of the present invention is to provide a method and device for processing database operation commands to solve the above problems.

In order to achieve the above purpose, according to one aspect of the present invention, a method for processing database operation commands is provided.

The processing method of the database operation command according to the present invention includes: encapsulating the database operation command; calling the encapsulated database operation command.

Preferably, before encapsulating the database operation command, the method further includes: receiving the database operation command.

Preferably, the database operation commands include one of the following types: insert operation commands, modify operation commands, delete operation commands, and query operation commands.

Preferably, when the database operation command is one of the insert operation command, modify operation command and delete operation command, the method further includes: judging whether there is an exception when executing the database operation command; Rollback; if there is no exception, submit the data.

Preferably, after the data is submitted, the method further includes: returning an execution result of calling the encapsulated database operation command.

Preferably, when the database operation command is a query operation command, the method further includes: judging whether there is an exception when executing the database operation command; if there is no exception, returning the result of executing the query operation command.

Preferably, invoking the encapsulated database operation command includes: creating an entity class of the database.

Preferably, invoking the encapsulated database operation command includes setting the following conditions for invoking: the name of the table for invoking the database operation command, the field to be operated, and the type of operation.

In order to achieve the above purpose, according to another aspect of the present invention, a processing device for database operation commands is provided.

The processing device of the database operation command according to the present invention includes: an encapsulation module for encapsulating the database operation command; and a calling module for invoking the encapsulated database operation command.

Preferably, the processing device further includes: a judging module, configured to judge whether there is an abnormality when executing the database operation command.

Through the present invention, by encapsulating the database operation command and calling the encapsulated database operation command, the problem of relatively complicated operation on the database is solved, and the effect of simply realizing the operation on the database is achieved.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is the flow chart of the processing method of the database operation order according to the embodiment of the present invention;

Fig. 2 is a flow chart of a preferred processing method of a database operation command according to an embodiment of the present invention;

Fig. 3 is a schematic diagram of an apparatus for processing database operation commands according to an embodiment of the present invention.

Detailed ways

It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and examples.

According to an embodiment of the present invention, a method and device for processing a database operation command are provided.

FIG. 1 is a flowchart of a method for processing database operation commands according to an embodiment of the present invention.

As shown in Figure 1, the method includes the following steps S202 to S204:

Step S102, encapsulating the database operation command;

Step S104, calling the encapsulated database operation command.

Preferably, before encapsulating the database operation command, the method further includes: receiving the database operation command.

Preferably, the database operation commands include one of the following types: insert operation commands, modify operation commands, delete operation commands, and query operation commands.

Preferably, when the database operation command is one of the insert operation command, modify operation command and delete operation command, the method also includes: judging whether there is an exception when executing the database operation command; The data is rolled back; if there is no exception, the data is submitted.

Preferably, after the data is submitted, the method further includes: returning an execution result of calling the encapsulated database operation command.

Preferably, when the database operation command is a query operation command, the method further includes: judging whether there is an exception when executing the database operation command; if there is no exception, returning the result of executing the query operation command.

Preferably, invoking the encapsulated database operation command includes: creating an entity class of the database.

Preferably, invoking the encapsulated database operation command includes setting the following conditions for invoking: the name of the table for invoking the database operation command, the field to be operated, and the type of operation.

The implementation process of the embodiment of the present invention will be described in detail below with reference to examples.

Fig. 2 is a flowchart of a preferred processing method of a database operation command according to an embodiment of the present invention.

The processing method of the database operation command of the present invention provides an object-oriented encapsulation method of the database operation, provides developers with a unified database operation entry, improves the efficiency of software development, and thus improves the stability of the software. There are four main types of database operations: INSERT, UPDATE, DELETE, and SELECT.

As shown in Figure 2, the method includes the following steps:

Step S201, creating an entity class. After the database receives the operation request, create the entity class of the database;

Step S202, setting the name of the database table to be operated;

Step S203, setting database fields and values to be queried and modified;

Step S204, setting conditions (when querying, modifying, deleting);

Step S205, database data command processing, that is, performing corresponding operations on the database;

Step S206, inserting the INSET operation command, and then turning to step S210;

Step S207, modify the UPDATE operation command, and then proceed to step S210;

Step S208, delete the DELETE operation command, and then turn to step S210;

Step S209, select the SELECT operation command, then proceed to step S211;

Step S210, setting the database operation command to submit automatically;

Step S211, spelling SQL statements;

Step S212, setting Prepared Statement data;

Step S213, execute the database operation command;

Step S214, judging whether the operation command is abnormal, if abnormal, go to step S215, otherwise, go to step S216;

Step S215, rolling back data;

Step S216, submit the data, then enter step S217;

Wherein, step S218 to step S221 are the same as step S211 to step S214;

Step S221, judging whether the operation command is abnormal, if abnormal, end the operation command, otherwise, go to step S217;

Step S217, return the result.

Preferably, the analysis of the four database operations is implemented, and the statement analysis process of the four database operations is as follows:

insert INSERT

The INSERT statement is as follows:

INSERT INTO USER(SERID, USERNAME, PASSWORD)

VALUES(100, 'test', 'test')

For the Insert statement, mainly the table name, field name, and field value, we create an entity class:

Class EntityClass is the entity class of the database table.

private HashMap<String, Integer>intMap=null;//map of integer fields and values

private HashMap<String, String> stringMap=null; // map of string fields and values

private HashMap<String, Date> dateMap=null; // date field and value.

private HashMap<String, Float>floatMap＝null;//private String tableName＝null for floating-point fields and values;//database table name

By initializing the table name of the setting class, it indicates which table needs to be operated, and then sets the field value, so that the operation of inserting into the database can be completed. For the ID generation, the database can be automatically generated or the maximum value can be increased by 1.

The operation method is:

EntityClass entityClass = new EntityClass("USER");

entityClass. put("USERID", "userid");

entityClass. put("USERNAME", "username");

entityClass. put("PASSWORD","password");

EntityDAO.getInstance().save(entttyClass);

delete DELETE

The DELETE statement is as follows:

DELETE FROM USER WHERE ID＝123

For the delete delete operation, only a table name and a query condition are required, so some of them can also be encapsulated by the above entity class.

The encapsulation method is:

EntityClass entityClass = new EntityClass("USER");

entityClass.setId(123);

EntityDAO.getInstance().delete(entityClass);

For complex batch deletion, you can also specify a query condition to delete. See the query SELETE statement for the query condition. The basic call statement is:

EntityDAO.getInstance().delete(entityClass, criteria); //criteria is the query condition.

Modify UPDATE

The Update statement is as follows:

UPDATE USER SET EMAIL＝’aaa@aaa.com’ WHERE ID＝123

For the update operation, it consists of three parts: the table name, the field name and value to be updated, and the update condition. Therefore, it can also be encapsulated by the above method. The package is as follows:

EntityClass entityClass = new EntityClass("USER");

entityClass.put("EMAIL", "aaa@aaa.com");

entityClass.setId(123);

EntityDAO.getInstance().update(entityClass);

At the same time, for batch updates, you can also specify a query condition to update. The basic call statement is:

EntityDAO.getInstance().update(entityClass, criteria); //criteria is the query.

QuerySELECT

The Select statement is as follows:

SELECT USERID, USERNAME, EMAIL FROM USER WHEREUSERNAME like='%王%';

For the update operation, there are table names, query fields, and query conditions. The query conditions are also composed of field names, conditions, and field values, so the query condition class is defined as follows:

The class Condition is a conditional class, which mainly has the following attributes

private String fieldname=null;//field name

private String stringValue=null;//Field value of string

private Integer[]inIntList＝null;//integer array, used for in operation

private String[]inStringList＝null;//String array, used for in operation

private Date dateValue=null;// field value of date

private Integer intValue=null;//integer field value

private Float floatValue=null;//floating point number

Class Criteria is a collection of conditions, mainly has the following methods:

List<Condition>expressionlist＝null;//query condition list

List<Order>orderlist=null;//Sorted list

Class ConditionGroup condition group, through ConditionGroup, Condition, Criteria three classes can form complex query conditions, to meet various database queries.

The encapsulation method is as follows:

EntityClass entityClass = new EntityClass("USER");

entityClass.putField("USERID");//Set the query field

entityClass.putField("USERNAME");//Set the query field

entityClass.putField("EMAIL");//Set query field

Criteria criteria = new Criteria();

criteria.add(Expression.like("USERNAME","King"));//Set like query conditions

List<EntityClass>

list = EntityDAO.getInstance().findAll(entityClass, criteria);

//criteria is the query condition.

The returned result is a list of entity classes. For the query of multiple tables, multiple tables can be specified when specifying the table name. At the same time, the entity class of the query can also specify the SQL conditions for the intersection of several tables.

Preferably, the method is based on the object-based encapsulation of database operations in the JAVA environment, which requires JDK1.5 or above. Preferred embodiments are as follows:

Preferably, take adding, deleting, modifying, and querying the data table User as an example:

The data structure of the table User is:

ID Number(10, 0) NOT NULL PRIMARY KEY,

USERID VARCHAR2(40) NOT NULL,

USERNAME VARCHAR2(40) NOT NULL,

PAS SWORD VARCHAR2(20) NOT NULL,

EMAIL VARCHAR2(100)NULL

Increase

Add a piece of data.

EntityClass entityClass = new EntityClass("USER");

entityClass. put("USERID", "userid");

entityClass. put("USERNAME", "username");

entityClass. put("PASSWORD","password");

entityClass. put("EMAIL","email");

EntityDAO.getInstance().save(entityClass);

delete

Delete a user whose ID is 123.

EntityClass entityClass = new EntityClass("USER");

entityClass.setId(123);

EntityDAO.getInstance().delete(entityClass);

Delete all users with the surname "王".

EntityClass entityClass = new EntityClass("USER");

Criteria criteria = new Criteria();

criteria.add(Expression.rightlike("USERNAME","King"));//Set like query conditions.

EntityDAO.getInstance().delete(entityClass, criteria);

Revise

Change the EMAIL of the user whose ID is 123 to a.a@a.com.

EntityClass entityClass = new EntityClass("USER");

entityClass.put("EMAIL", "aaa@aaa.com");

entityClass.setId(123);

EntityDAO.getInstance().update(entityClass);

Change all emails surnamed Wang to a.a@a.com.

EntityClass entityClass = new EntityClass("USER");

entityClass.put("EMAIL", "aaa@aaa.com");

Criteria criteria = new Criteria();

criteria.add(Expression.rightlike("USERNAME","King"));//Set like query conditions.

EntityDAO.getInstance().update(entityClass, criteria);

Inquire:

Query all users with the surname Wang:

EntityClass entityClass = new EntityClass("USER");

entityClass.putField("*");//Set the query field.

Criteria criteria = new Criteria();

criteria.add(Expression.rightlike("USERNAME","King"));//Set like query conditions.

List<EntityClass>

list = EntityDAO.getInstance().findAll(entityClass, criteria);

//criteria is the query condition.

If another table (USERINFO) has other information such as the user's age, this table has two fields:

ID NUMBER(10,0) NOT NULL,

AGE NUMBER(3,0) NOT NULL

The calling method is as follows:

EntityClass entityClass = new EntityClass("USER, USERINFO");

entityClass.setJoinCondition("USER.ID=USERINFO.ID);

entityClass.putField("AGE");//Set the query field

entityClass.putField("USERNAME");//Set the query field

entityClass.putField("USERID");//Set the query field

entityClass.putField("PASSWORD");//Set the query field

Criteria criteria = new Criteria();

criteria.add(Expression.rightlike("USERNAME","King"));//Set like query conditions.

List<EntityClass>

list = EntityDAO.getInstance().findAll(entityClass, criteria);

//criteria is the query condition.

From the above description, it can be seen that the present invention achieves the following technical effects: using the existing technology to realize the object-oriented processing method of database data commands, developers can quickly grasp the programming of the database, improve the efficiency of programming, and ensure The reusability of data layer operations improves the stability of the software. Including the uniform encapsulation of database operation commands to ensure the reusability of the database operation layer and the stability of the system; developers can complete database operations regardless of SQL syntax; all operations use PreparedStatement to improve database operations Excellent performance; simple call, easy to use; simple integration environment; support arbitrary complex queries.

According to an embodiment of the present invention, a processing device for a database operation command is provided.

It should be noted that the steps shown in the flowcharts of the accompanying drawings may be performed in a computer system, such as a set of computer-executable instructions, and that although a logical order is shown in the flowcharts, in some cases, The steps shown or described may be performed in an order different than here.

FIG. 3 is a schematic diagram of an apparatus for processing database operation commands according to an embodiment of the present invention.

As shown in FIG. 3 , the device includes: an encapsulation module 301 and a calling module 302 .

Encapsulating module 301, encapsulating the database operation command;

The calling module 302 is used to call the encapsulated database operation command.

Preferably, the processing device further includes: a judging module 303 .

A judging module 303, configured to judge whether there is an exception when executing the database operation command.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Optionally, they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be made into individual integrated circuit modules, or they can be integrated into Multiple modules or steps are fabricated into a single integrated circuit module to realize. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a database manipulation process of commands method is characterized in that, comprising:

The database operational order is encapsulated;

Described database manipulation order after the encapsulation is called.

2. disposal route according to claim 1 is characterized in that, before the database operational order was encapsulated, described method also comprised:

Receive described database manipulation order.

3. disposal route according to claim 1 is characterized in that, described database manipulation order comprises one of following kind:

Insert operational order, retouching operation order, deletion action order, query manipulation order.

4. disposal route according to claim 3 is characterized in that, is that described method also comprises under the situation of one of described insertion operational order, described retouching operation order and described deletion action order in described database manipulation order:

When carrying out described database manipulation order, judge whether to exist unusual;

Exist under the unusual situation, then carrying out data rewind;

Not existing under the unusual situation, then submit described data to.

5. disposal route according to claim 4 is characterized in that, after submitting described data to, described method also comprises:

Return the execution result that the described database manipulation order after the encapsulation is called.

6. disposal route according to claim 3 is characterized in that, is under the situation of query manipulation order in described database manipulation order, and described method also comprises:

When carrying out described database manipulation order, judge whether to exist unusual;

Do not exist under the unusual situation, then returning the result who carries out described query manipulation order.

7. disposal route according to claim 1 is characterized in that, the described database manipulation order after the encapsulation is called comprise:

Create the entity class of database.

8. disposal route according to claim 1 is characterized in that, the following condition that is provided for calling that comprises is called in the described database manipulation order after the encapsulation:

Call the table name of described database manipulation order, field and the operation species that need operate.

9. a database manipulation process of commands device is characterized in that, comprising:

Package module encapsulates the database operational order;

Calling module is used for the described database manipulation order after the encapsulation is called.

10. treating apparatus according to claim 9 is characterized in that, described treating apparatus also comprises:

Judge module, be used for judging when carrying out described database manipulation order, whether exist unusual.

Images