JP2004302840A - Data base access method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method of unifying different data base access systems by one interface and an automatic creating method of a data base operation procedure therefor. <P>SOLUTION: A user program 580 converts a data base operation type and data received from a client 20 into a data base operation procedure in conformity with a corresponding data base access system using a previously-automatically created table class 541, table collection class 542 and table access class 543, and issues an access request to a DB 10 using the data base operation procedure. As a result, a plurality of data base access systems are easily used properly by the same interface, thereby enabling the reduction in the burden on a software developer. A data base user also easily uses a data base. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a database access method for enabling access to a database by a plurality of different database access methods using the same interface.
[0002]
[Prior art]
In order to access a database, a database operation procedure that conforms to the rules defined as the database access method to be used must be described. Therefore, for example, when registering a large amount of data in a database, the data is registered in a batch process using an SQL (Structured Query Language) loader that can perform registration processing at high speed. However, when searching or updating a database, it is not possible to use an SQL loader having only a registration function. Therefore, software of another database access method such as JDBC (Java (registered trademark) DataBase Connectivity) is used. To access the database. As described above, in order to access a database using a plurality of different database access methods, a database operation procedure conforming to the format specified by each database access method is described. Had to be used properly.
[0003]
As a result, in conventional database access using a plurality of different database access methods, there are problems in that the development work of application software and the like by software developers becomes complicated and database access is troublesome for database users. there were. In addition, a person must manually define a class or the like according to the table structure of the database, which is troublesome. Note that Patent Document 1 is disclosed as a conventional technique.
[0004]
[Patent Document 1]
JP-A-5-197600
[Problems to be solved by the invention]
The present invention has been made in view of the above problems, and in order to facilitate access to a database using a plurality of different database access methods, a database that is unified with one interface even if the database access method is different. It is an object of the present invention to provide a method for automatically accessing a database and a method for automatically generating a class and a database operation procedure therefor.
[0006]
[Means for Solving the Problems]
SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an invention according to claim 1 is a database access method for accessing a database using a plurality of different database access methods, wherein the database is accessed from a terminal. For receiving data and database operation type, identify the received database operation type, the data and the database into a database access format that conforms to a predetermined rule determined by the database access method corresponding to the identified data operation type A database access method comprising converting a database operation type and issuing an access request to the database using the database access format.
[0007]
According to a second aspect of the present invention, in the database access method according to the first aspect, the conversion into the database access format is a table class for storing the received data in the same format as a corresponding table in the database. And a control table access class corresponding to the database access method is generated in advance in association with the database table, the received data is stored in the corresponding table class, and the identified data operation type is stored. The data and the database operation type are converted according to the predetermined rule described in the table access class corresponding to.
[0008]
According to a third aspect of the present invention, in the database access method according to the second aspect, the generation of the table class and the table access class is performed by preparing a table class generating template file corresponding to a table of the database. , And a table access class template file prepared in advance corresponding to the database access method, and attribute information of the database.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a database access method according to an embodiment of the present invention will be described. Here, a database access method to which the present invention is applied when two types of database access methods (JDBC and SQL loader) are used will be described with reference to FIG. FIG. 1 is a block diagram showing an entire system according to an embodiment in which the present invention is applied to an application server (AP server). In FIG. 1, reference numeral 10 denotes a database (DB) for storing various data. Reference numeral 20 denotes a client (terminal) used when a user accesses the DB 10, and reference numeral 30 denotes an in-house system that performs various processes using the DB 10. Reference numeral 50 denotes an AP server that provides various application services to which the present invention is applied. The AP server 50 includes a Web DB access unit 540 that executes Web (online) functions and a batch DB access unit that executes batch functions. It comprises a unit 560 and a user program 580 (corresponding to a database access unit described in the claims).
[0010]
The Web DB access unit 540 enables all operations of search, update, registration, and deletion for the DB 10 using JDBC. On the other hand, the batch DB access unit 560 enables only the registration operation to the DB 10 using the SQL loader. Therefore, the batch DB access unit 560 can perform a registration operation in the DB 10 faster than the Web DB access unit 540. Further, the user program 580 controls an interface with the client 20 and the in-house system 30, and controls the Web DB access unit 540 and the batch DB access unit 560 to access the DB 10.
[0011]
Each processing unit shown in FIG. 1 may be realized by dedicated hardware, and these processing units are configured by a memory and a CPU (Central Processing Unit). May be implemented by loading a program (not shown) for realizing the function into a memory and executing the program. The storage unit (not shown) includes a nonvolatile memory such as a hard disk device, an optical disk device, or a flash memory, a volatile memory such as a RAM (Random Access Memory), or a combination thereof. I do.
[0012]
Also, a program for realizing the function of each processing unit in FIG. 1 is recorded on a computer-readable recording medium, and the program recorded on this recording medium is read into a computer system and executed, thereby executing each processing unit. May be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices.
[0013]
Next, an outline of the operation of the embodiment of the present invention will be described with reference to FIG. In FIG. 1, when data is registered in the DB 10 when accessing the DB 10 from the client 20 or the in-house system 30, the client 20 or the in-house system 30 specifies whether to use the JDBC or the SQL loader, The user program 530 selects either the Web DB access unit 540 or the batch DB access unit 560 corresponding to the specified JDBC or SQL loader, and selects the selected Web DB access unit 540 or batch DB access unit 560. It controls and accesses the DB 10 to register data. When any of search, update, and delete is performed on the DB 10, the DB 10 is accessed by the Web DB access unit 540 using JDBC under the control of the user program 580 to perform search, update, or delete processing. Perform The details of these operations will be described later.
[0014]
Next, automatic generation of a DB access class in the Web DB access unit 540 and the batch DB access unit 560 in FIG. 1 will be described with reference to FIG. 2, the same parts as those in FIG. 1 are denoted by the same reference numerals, and the description thereof will be omitted. FIG. 2 is a diagram illustrating a mechanism for automatically generating a DB access class by a DB access class automatic creation program. Here, the DB access class is a class for storing data as information necessary for accessing the DB 10, a table name, data such as database operation contents, and control information.
[0015]
In FIG. 2, a DB 10 holds attribute information 11 in addition to data. The attribute information 11 is information on a table stored in the DB 10, such as a table name, a column name, and a data type. Reference numeral 510 is a generic name of template files composed of six types of template files necessary for automatically generating the DB access class 530. Reference numeral 511 denotes a table class generation template file for generating a table class 541 corresponding to the table name of the attribute information 11 of the DB 10, and a replacement character string for replacing the attribute information 11 of the DB 10 in the file. Is embedded. Reference numeral 512 denotes a collection class generation template file for generating the table collection class 542, in which a replacement character string for replacement with the attribute information 11 is embedded.
[0016]
Reference numeral 513 denotes a template file for generating a table access class 543 for generating a table access class 543, in which a replacement character string for replacing the attribute information 11 is embedded. Reference numeral 514 denotes an SQL loader execution class generation template file for generating the SQL loader execution class 561, and a replacement character string for replacement with the attribute information 11 is embedded therein. Reference numeral 515 denotes a CTL file generation template file for generating the CTL file 562, in which a replacement character string for replacement with the attribute information 11 is embedded. Reference numeral 516 denotes a template file for generating a registration data CSV file creation class 563, in which a replacement character string for replacement with the attribute information 11 is embedded.
[0017]
Reference numeral 520 denotes a DB access class automatic generation program for automatically generating the DB access class 530 using the template file 510 and the attribute information 11 such as the table name, column name, and data type acquired from the DB 10 as input information. The DB access class 530 is a generic term for various classes that are configured from the classes of the Web DB access unit 540 and the batch DB access unit 560, and that have information necessary for accessing the DB 10.
[0018]
The classes of the Web DB access unit 540 that performs access processing to the DB 10 using JDBC include a table class group 541g, a table collection class group 542g, and a table access class group 543g. Here, the table class group 541g, the table collection class group 542g, and the table access class group 543g are classes having the same number of table classes 541, table collection classes 542, and table access classes 543 as the number of tables in the DB 10.
[0019]
The table class 541 is a class corresponding to the table of the DB 10 and sets key items, update data, and registration data to be sent to the table access class 543. The table collection class 542 is a class that can have a plurality of table classes 541 in a vector type and is intended to simplify the handling of data of a plurality of rows having the same face (the table class 541 and the table collection class 542). Is equivalent to the table class described in the claims). The table access class 543 is a control class for accessing the DB 10 using JDBC.
[0020]
Further, the batch DB access unit 560 that performs an access process to the DB 10 using the SQL loader includes a SQL loader execution class group 561g, a CTL file group 562g, and a registration data CSV file creation class group 563g. Here, the SQL loader execution class group 561g, the CTL file group 562g, and the registration data CSV file creation class group 563g are a SQL loader execution class 561, a CTL file 562, and a registration data CSV file creation class 563, respectively. We have only number. The SQL loader execution class 561 is a control class for accessing the DB 10 using the SQL loader. The CTL file 562 is a setting file necessary for using the SQL loader. The registration data CSV file creation class 563 is a control class for creating registration data to be sent to the SQL loader execution class 561 as a CSV file.
[0021]
Next, an operation of automatically generating a DB access class will be described with reference to FIG. 2, first, the DB access class automatic generation program 520 connects to the DB 10 (step S1) and acquires the attribute information 11 from the DB 10 (step S2). Further, the DB access class automatic generation program 520 reads the table class generation template file 511 and replaces the replacement character string in the table class generation template file 511 with the attribute information 11 acquired in step S2. Create a class 541. This is repeated for the attribute information 11, that is, the number of tables, to create a table class group 541g (step S3). Details of creation of this table class will be described later using a specific example.
[0022]
The DB access class automatic generation program 520 similarly generates the table collection class generation template file 512, the table access class generation template file 513, the SQL loader execution class generation template file 514, and the CTL file generation. Based on the template file 515, the template file 516 for creating a registration data CSV file, and the attribute information 11, a table collection class group 542g, a table access class group 543g, an SQL loader execution class group 561g, CTL A file group 562g and a registration data CSV file creation class group 563g are created (steps S4 to S8), and the generation of the DB access class 530 ends.
[0023]
Next, FIGS. 3 and 4 show an example in which a table class (file) 541 is created from the table class generation template file 511 by the DB access class automatic generation program 520 described in FIG. FIG. 3 is a diagram showing an example of a template file 511 for extracting the attribute information 11 of the database DB 10 and generating a table class (extracting related portions). FIG. 4 shows an example of a created table class (file) 541 (related). FIG. The replacement character string portion in the table class generation template file 511 shown in FIG. 3 is replaced by the contents of the corresponding attribute information 11 in the DB 10 to create the table class (file) 541 shown in FIG.
[0024]
For example, since “Table” in “public class Table% TABLE_NAME%} on the third line in FIG. 3 indicates that the replacement character string% TABLE_NAME% is to be replaced with the table name of the attribute information 11, this part is replaced with a table. The name is replaced with USER, and as shown in the third line of FIG. 4, it is converted to public class TableUSER. Other replacement character strings in the table class generation template file 511 are similarly replaced, and a table class (file) 541 is created. Further, other classes such as the table collection class 542 shown in FIG. 2 are created in the same manner as the table class 541.
[0025]
Next, an operation for registering data in the DB 10 will be described with reference to FIG. FIG. 5 is a diagram showing a flow of operation when data is registered in the DB 10 from the client 20. 5, the same parts as those in FIG. 1 or FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted. In FIG. 5, upon receiving data to be registered from the client 20 (step S50), the user program 580 sets the received data in the table class 541. At this time, if the received data has a plurality of rows, one row of data is set to one table class 541, and therefore the number of table classes 541 is set to the number of rows (step S51). ).
[0026]
Further, the user program 580 sets all the set table classes 541 to the table connection class 542 (step S52). Then, the user program 580 identifies the method (function) (database operation type) for operating the database, which is received together with the data in step S50, and classifies the corresponding JDBC or SQL loader method into a table access class based on the result. 543 (step S53). The called method of the table access class 543 registers data in the DB 10 by a predetermined method (step S54).
[0027]
Next, the registration operation to the DB 10 described in FIG. 5 will be described in further detail. Here, it is assumed that two data are registered in a table whose table name is “user” stored in the DB 10 using the JDBC and the SQL loader. First, an operation when data is registered in the DB 10 using JDBC will be described with reference to FIG. FIG. 6 is a diagram showing an image of a method of a DB access class using JDBC. In FIG. 6, a user table class 541u is a table class corresponding to the “user” table of the DB 10, and a user table collection class 542u is a collection class of the user table class 541u.
[0028]
In FIG. 6, the user program 580 stores two data of the user number 11 and the user number 12 each composed of the user number, last name, name and mail address received from the client 20, respectively, with the corresponding user number of the user table class 541u, The user table class 541u is set in the user name, name, and mail address fields (step S61), and is sequentially set in the user table collection class 542u (step S62). Also, the JDBC method insertTableUsers for registering data is called with the object name tableUsers of the user table collection class 542u as an argument (step S63).
[0029]
Then, the user program 580 extracts the corresponding user table class 541u from the user table collection class 542u of the object name tableUsers passed as an argument in order to create an SQL statement corresponding to the called insertTableUsers method (step S64). ), A user name, a surname, a name, and a table name corresponding to a mail address set in the user table class 541u are set in predetermined portions of an SQL statement INSERT for creating a table name, and two SQL statements are created (step S65). ). By accessing the DB 10 using these two SQL statements, two data are registered in the DB 10.
[0030]
Next, an operation of registering data in the DB 10 using the SQL loader will be described with reference to FIG. 7, the same parts as those in FIG. 6 are denoted by the same reference numerals. FIG. 7 is a diagram showing an image of a method of the DB access class using the SQL loader. In FIG. 7, the user program 580 stores two data of the user number 11 and the user number 12, which are composed of the user number, last name, name, and mail address received from the client 20, respectively, with the corresponding user number of the user table class 541u, The information is set in the fields of first name, last name, and mail address (step S71), and is set in the user table collection class 542u (step S72). Then, the method "appendTableUsers" of the SQL loader to be registered is called with the object name "tableUsers" of the user table collection class as an argument (step S73).
[0031]
Next, the user program 580 extracts the corresponding user table class 541u from the user table collection class 542u of the object name tableUsers passed as an argument of the called appendTableUsers method (step S74), and is set in the user table class 541u. A CSV file is output using the current user number, last name, first name, and mail address (step S75). Further, the user program 580 creates an SQL loader command using the user table class 541u (Step S76) and executes it. Thereby, the two data in the CSV file are registered in the DB 10.
[0032]
In this way, the method insertTableUser (tableUsers tables) for calling JDBC and the method applicableTableUsers (tableUsers tables) for calling SQL loader are different in the JDBC and SQL loader, but the method where le is the same as the argument sab is the same as the argument sab t sab Therefore, application software developers and database users need only be aware of the JDBC and SQL loader method names.
[0033]
【The invention's effect】
As described above, according to claims 1 and 2 of the present invention, a database operation type received from a terminal is identified using a table class and a table access class generated in advance, and the data operation type corresponding to the database operation type is identified. The received database operation type and data are converted into a database access format conforming to the database access method described above, and an access request is issued to the database using the database access format. As a result, a plurality of database access methods can be easily used properly with the same interface, and the burden of development work of software developers such as application software can be reduced. Also, users of the database can easily use the database. Furthermore, by unifying the rules for accessing the database, the processing structure can be easily understood, and work efficiency and maintainability can be improved.
According to the third aspect of the present invention, the table class and the table access class are generated in advance according to the table class generating template file prepared in advance corresponding to the database table and the database access method. It is automatically generated based on the prepared table access class generation template file and the attribute information stored in the database in advance. As a result, there is no need for a person to manually define a class or the like according to the table structure, and in particular, a database having a large number of tables can greatly reduce the trouble.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a system to which a database access method according to an embodiment of the present invention is applied.
FIG. 2 is a diagram showing a mechanism for automatically generating a DB access class according to the embodiment;
FIG. 3 is a view showing an example of a template file for generating table classes according to the embodiment;
FIG. 4 is a diagram showing an example of a table class (file) according to the embodiment.
FIG. 5 is a diagram showing an operation flow when data is registered in a database from a client according to the embodiment.
FIG. 6 is a diagram showing an image of a method of a DB access class using JDBC according to the embodiment.
FIG. 7 is a diagram showing an image of a method of a DB access class using an SQL loader according to the embodiment.
[Explanation of symbols]
Reference Signs List 10: database (DB), 20: client, 30: in-house system, 50: AP server (application server), 510: template file, 520: DB access class automatic generation program, 530: DB access class, 540: Web DB Access unit, 560: Batch DB access unit, 580: User program

Claims (3)

In a database access method for accessing a database using a plurality of different database access methods,
The terminal receives data and a database operation type for accessing the database from the terminal, identifies the received database operation type, and conforms to a predetermined rule defined by a database access method corresponding to the identified data operation type. A database access method comprising: converting the data and the database operation type into a database access format; and issuing an access request to the database using the database access format. The conversion to the database access format is performed by storing a table class for storing the received data in the same format as the corresponding table of the database and a table access class for control corresponding to the database access method, Is generated in advance in association with, the received data is stored in the corresponding table class, the data and the data according to the predetermined rule described in the table access class corresponding to the identified data operation type 2. The database access method according to claim 1, wherein a database operation type is converted. The generation of the table class and the table access class includes a table class generation template file prepared in advance corresponding to the database table, and a table access class template file prepared in advance corresponding to the database access method. 3. The database access method according to claim 2, wherein the information is generated based on attribute information of the database.

Images