JP5336827B2 - Information processing apparatus, database system, information processing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processor that is adaptable to multilanguage, a database system, and an information processing method, and program. <P>SOLUTION: The information processor includes: a client connection processing part 116 for setting a language identification value for designating a language environment of a client in a language setting part 120 for setting the language environment while identifying the language environment of the client who accesses the information processing device; a command processing part 118 which inspects script included in an access request, and determines the existence of a command that requests multilanguage processing; and a language resource processing part 126 which receives a command to allow a database to be accessed in the language environment set in the language setting part when determining that the command processing part 118 requests the multilanguage processing. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  More particularly, the present invention relates to an information processing apparatus, a database system, and information that determine information about a language type received by the information processing apparatus and provide information on the language type. The present invention relates to a processing method and a program.

  Now that wide-area networks such as the Internet are widespread and broadband communications are also widespread, it is necessary to assume that information processing devices such as servers that store and distribute information are accessed from a plurality of language zones. Therefore, a person who intends to provide content via an information processing apparatus such as a web server identifies the language of the content request, searches for the content translated into the language, and retrieves the searched content for the request source. Processing to return to.

  Conventionally, in order to search for content, the information processing apparatus, after determining the language of the content request, redirects to the database server that manages the content in the language using URL redirection and executes the search for the translated content The retrieved content is returned to the information processing apparatus. The information processing apparatus executes a process of returning the content received from the database server to the content request source, thereby enabling the content corresponding to the language used by the content request source to be sent.

  For this reason, in conventional multilingual support, web pages of different languages are created for the same content, and a plurality of different language contents translated in different languages are generated for each web page. It was necessary to index each and configure a separate database. As a result, database vendors and vendors of information processing apparatuses are required to configure a plurality of databases that overlap in terms of data contents and to perform indexing for the same content.

  Also, for example, static messages that are not added in chronological order as in the case of help display for a specific application program, etc., help messages translated into each language to execute multilingual processing Resource files can be prepared. For this purpose, for example, an information processing apparatus implements a function such as a ResourceBundle of Java (registered trademark), and extracts and displays a resource file corresponding to the language system used by the user.

  On the other hand, in information processing apparatuses that provide content on a network such as a web server, in recent years, dynamic contents such as forums and blogs whose contents are updated according to transactions between users or between users and information processing apparatuses The utilization ratio of is also increasing. In addition, with the spread of the Internet, the types and number of contents uploaded to a database as web contents are rapidly increasing.

  For such contents, it is difficult to predict resource files in advance, and more efficient language handling processing is required. Even if a web server or other web service is not assumed, for example, when managing employees who use multiple languages in a multinational company, the database written in multiple languages is similarly rebuilt. The need arises for schema changes, increased data redundancy, and data synchronization issues.

  This is because the conventional multilingual processing translates content into different languages to provide the same content for each language such as English, Japanese, Chinese, German, French, Italian, etc. Need to be databased and indexed. For this reason, an increase in the number of language types that the information processing apparatus should support is accompanied by an increase in data redundancy, and each indexing process is also required, and a data synchronization process between the databases is also required. For this reason, coupled with an increase in the amount of content transferred via the network, conventional multilingual processing has been a cause of increasing the processing load on the information processing apparatus. On the other hand, there is a conventional technique for managing multilingual information in the same database in order to eliminate the above-described data redundancy.

  FIG. 27 shows a data structure of a conventional database used for multilingual correspondence. The conventional example shown in FIG. 27 shows the data structure of an employee database in a multinational company, and is a conventional example when a plurality of languages are managed by a single database. In the data structure of FIG. 27 (a), an English notation “John” is given to an employee number, and contact information such as an organization code and a telephone number are associated with each other.

  FIG. 27B shows a data structure in which the same information described in multiple languages is registered in the single database shown in FIG. As shown in FIG. 27B, for the employees identified by the same employee number, a record for registering “John” in English and a record for registering “John”, which is a translation in Japanese, are generated separately. For each record, the language identification value that specifies the language is registered as “en” or “ja”.

  As shown in FIG. 27 (b), the employee number used as the primary key in FIG. 27 (a) to identify the employee can no longer uniquely identify the record. . For this reason, in order to refer to the same content corresponding to a plurality of languages in the same database, in the conventional example shown in FIG. 27B, the primary key must be expanded to {employee number + language}. I understand that it doesn't become. As a result, the application that accesses this table needs to be corrected. In addition, when there is no data in the language desired by the application, it is necessary to implement processing such as what to do, which increases the design / development / maintenance cost of the application in addition to the design cost of the database.

  In addition, despite the use of a single database, the number of records that register the same content is increased by the number of languages to be supported, and in the end, it gives redundancy that is not much different from when multiple databases are formed. become. In addition, search sentences such as indexing and SQL are also accompanied by an increase in processing overhead that must be performed in accordance with the language of the search request or content request. Furthermore, it has been necessary to implement a corresponding process independently of the database as to how the search application or the web application will respond when the corresponding language is not registered.

  Further, as shown in FIG. 27C, in order to eliminate data redundancy, a field described in multiple languages may be managed by another table linked with a primary key such as an employee number. ing. Even in this case, after all, it is necessary to join multiple tables and join each table using the primary key, which increases the database design cost and application design / development / maintenance cost. This is the same as the conventional example described with reference to FIG.

  Until now, a technology for providing a language service corresponding to the language of each country has been proposed. For example, in Japanese Patent Laid-Open No. 2003-44474 (Patent Document 1), language information associated with a specific client and user information is changed. In order to provide dynamic language translation of a content part through the use of a dynamic translation service to be stored, the dynamic translation service determines a language based on client and user information and includes a content part of the content part. Skeleton content elements are determined based on client and user information using either a stored translation table for each skeleton content element or a dynamic natural language translation of each skeleton content element Translated into the selected language. A system is described in which translated skeleton content elements are subsequently integrated into the content portion.

  Patent Document 1 discloses that a client language environment is identified, translated into a language corresponding to the client language environment, and integrated into the content. However, how the translated content is managed and content is added. It is not disclosed whether to synchronize between translated words in response to the correction.

In Japanese Patent Laid-Open No. 5-242139 (Patent Document 2), a set of messages to be displayed and output is stored for each category and the number of national languages to be displayed, and the category designation of the message is output as the subcommand is activated. Disclosed is a display control system that refers to the national language designation of a message and generates a message database of the designated national language on a storage means by referring to a dictionary. Patent document 2 discloses the point of executing language translation on the application side that uses the database, but does not disclose how to manage the content corresponding to each language. It does not enable efficient national language support while streamlining content synchronization and improving data redundancy.
JP 2003-44474 A JP-A-5-242139

  As mentioned above, up to now, even if the number of language types to be supported increases, it eliminates data record redundancy and improves maintainability such as data synchronization without changing the main schema of the database. Furthermore, an information processing apparatus, a database system, an information processing method, and a program capable of handling a process without a corresponding language independently of a higher-level application are required.

  In order to register different language contents with different languages even though they are the same contents, the above-described conventional technique adopts a technical idea of generating independent records and registering them in a single or separate database. This is a problem. According to the present invention, the above-described problems of the prior art are an information processing apparatus and database capable of managing a plurality of languages on a single database without preparing a plurality of tables and records corresponding to the plurality of languages. It is solved by providing a system, an information processing method and a program.

  In the present invention, in order to achieve the above object, the information processing apparatus identifies the language environment of the client accessing the information processing apparatus, and specifies the language environment of the client in the language setting unit that sets the language environment. A client connection processing unit for setting a value is included.

  The information processing apparatus 110 includes a client connection processing unit that receives a connection from a client, a command processing unit that receives a command such as an SQL statement, and a register processing unit that performs processing when a change of the language environment processed by the command is requested When a command is a request to perform operations such as creating a table or inserting / updating / deleting / inquiring data on a table, values in multiple languages are managed from the table processing unit that performs the processing and columns of multiple tables. Implements a language resource processing unit that can access the resource table and performs processing when a command requests an operation on the resource table. This patent can be realized by extending an existing database system, and other commands received from the client are processed as usual.

  In the present invention, a resource column is implemented as a data type of a table column in order to store values in multiple languages, and the values in multiple languages can be managed by one column by using the column. . Further, it is also possible to separately manage only resources so that a plurality of columns can refer to the same resource, and refer to it from the plurality of columns. A resource is a set of values in a plurality of languages that are given meanings, for example, one that holds the name of the month in multiple languages, one that holds the name of a city in multiple languages, and the like. A table holding separately managed resources is called a resource table. As this usage form, if you keep a column of which city you work as the work location of the employee information table and keep a column of which city you live as the residence of the customer information table, You can define a resource with a city name in the language, and both columns can reference that resource.

  As a result, values written in different languages for the same value can be registered in the same column of a single table, and the increase in database design costs and application development / design / maintenance costs can be suppressed. .

The register processing unit holds various variables for each connected client. Two language identification registers are implemented as the variables. Hereinafter, the two language identification registers are referred to as a language identification register CHARSET and a default language identification register DEFAULT_CHARSET. The language identification register values CHARSET and DEFAULT_CHARSET are maintained for each connected client. The value of the language identification register CHARSET sets the default language that the client wants the database server to process. When the client connects to the database, the client language environment is set as the value of CHARSET. After that, if you want to change, SQL is the language change command introduced from the client in this embodiment, SET
It can be changed with CHARSET 'language identification value'.

  In the present invention, the command transmitted from the client can include the language (language identification value) that is desired to be processed, and if included, the processing for that language is performed. If it is not included, the language set in CHARSET is processed. Therefore, various applications can perform processing according to their own language without being aware of it, and an administrator can connect to a database and manipulate data in each language.

  The DEFAULT_CHARSET implemented in the language identification register is used to set a language value for substitution when the requested language data is not saved. There are two types of usage. First, when saving data, if the language to be saved is the same as the value registered in DEFAULT_CHARSET, it is also saved as the default value. When referring, it is saved if there is no data in the corresponding language. Is a way to get the default value. For example, when DEFAULT_CHARSET is set to English and English data is inserted, the data is saved as a default value.

  The other method is a method of acquiring data in the language set by DEFAULT_CHARSET secured in the language identification register when there is no data in the corresponding language when referring to the data. Below, it demonstrates based on the former.

  Furthermore, in the present invention, since a different client language environment is provided for each client, individual access is possible even in parallel access by a plurality of clients.

  By adopting the above configuration, according to the present embodiment, the data environment of the database for managing the contents corresponding to multiple languages is eliminated, the schema is simplified, and the client is aware of the language environment. An information processing apparatus, a database system, an information processing method, and a program that enable access to a database without being performed can be provided.

  Hereinafter, although this invention is demonstrated with embodiment, this invention is not limited to embodiment mentioned later. FIG. 1 shows an embodiment of a database system 100 of the present embodiment. The database system 100 is multilingual compatible with the information processing apparatus 110 that implements a relational database (hereinafter referred to as RDB), a table storage unit 130 that stores a table created by the RDB, and the present embodiment. And a language resource table storage unit 132 that stores language resources configured as a table having a data structure.

  The information processing apparatus 110 is connected to a network 112 including the Internet and a LAN as appropriate, and receives an access request from a client computer (not shown; hereinafter simply referred to as a client) via the network 112. And provide services such as table creation, editing, and search. Note that the table storage unit 130, the language resource / table storage unit 132, and the corresponding processing units described later are described as separate functional modules in FIG. It is also possible to adopt an integrated mounting format as the functional module.

  The language resource table storage unit 132 includes a resource information storage unit that stores each attribute value of data. The language resource table storage unit 132 includes a resource reference information storage unit, and the resource reference information storage unit manages information on resource columns that the database system 100 currently refers to. Used for exclusive control, history management, etc.

  In the embodiment shown in FIG. 1, the information processing apparatus 110 is configured as a server. When the information processing apparatus 110 is implemented as a server, the information processing apparatus 110 can be configured as a dedicated server that provides a distributed computing environment such as CORBA (Common Object Resource Broker Architecture), or uses the HTTP protocol. It can also be implemented as a web server that executes services such as file transfer and search. When implemented as a dedicated server, the information processing apparatus 110 accesses the information processing apparatus 110 using an API or a user interface provided by dedicated client software. When the information processing apparatus 110 is implemented as a web server, the client implements a web browser such as Internet Explorer (registered trademark), Firefox (registered trademark), Opera (registered trademark), and performs information processing. Allows access to device 110.

In addition, for the purpose of accessing the database processing module of the information processing apparatus 110, the client uses JDBC (Java (registered trademark) Database).
Implement APIs such as Connectivity and ODBC (Open Database Connectivity) as access protocols at the application level. When a client accesses a database application of the information processing apparatus 110, the client can access the information processing apparatus 110 using these APIs.

  Note that a local keyboard, mouse, display device, and the like are connected to the information processing apparatus 110 via a bus such as USB and XGA, and an administrator of the information processing apparatus 110 is locally connected to the information processing apparatus 110. It may be configured such that it can be accessed.

  The information processing apparatus 110 described above may be a CISC architecture microprocessor such as PENTIUM (registered trademark), XEON (registered trademark), CELERON (registered trademark), ATHRON (registered trademark), other PENTIUM (registered trademark) compatible chips, or RISC architecture processors such as POWER PC (R) can be implemented in single-core or multi-core form.

  In addition, the information processing apparatus 110 is controlled by an operating system such as WINDOWS (registered trademark) 200X, UNIX (registered trademark), LINUX (registered trademark), or the like, and includes C, C ++, JAVA (registered trademark), and JAVA (registered trademark). Implementing programming languages such as BEANS, PERL, RUBY, etc., loading various programs into an execution space such as a RAM, and causing the processor to execute the programs. Realize. The client is composed of a personal computer, a workstation, a PDA, a mobile phone, and the like, and accesses the information processing apparatus 110 under an appropriate OS to perform search, create a new table, and the like.

  Hereinafter, each functional unit of the information processing apparatus 110 will be described. Each processing unit of the information processing apparatus 110 is configured such that the information processing apparatus 110 reads and expands the program of the present embodiment and the conventional database application into an execution space such as a RAM, and the processor executes the program. The information processing apparatus 110 is realized as a functional unit that functions as each processing unit.

  The information processing apparatus 110 includes a network adapter 114, a client connection processing unit 116, and a command processing unit 118. The network adapter 114 receives an access request to the RDB sent via the network 112 and passes the content of the access request to each function unit that uses a higher-level protocol. In the present embodiment, the access request includes a request for searching the RDB in addition to a table creation / editing request for the RDB. In this embodiment, the client connection processing unit 116 determines the language environment used by the client, and executes processing corresponding to the access request. The client connection processing unit 116 implements the language setting unit 120 for this purpose. More specifically, the language setting unit 120 manages the register processing unit 120a and the language identification register 120b. The register processing unit 120a has a function of editing a memory area managed by the language setting unit 120, and sets the current language setting to the language identification register 120b corresponding to the client.

  When the client connects to the database, the client connection processing unit 116 uses the language information (hereinafter referred to as a language identification value) used by the client transmitted from the client to be managed by the register processing unit 120a. In the identification register 120b, the register processing unit 120a is requested to set the value of CHARSET in the language identification register. The register processing unit 120a sets the language used by the client to CHARSET as the value of the language identification register of the language identification register 120b. In the language identification register 120b, DEFAULT_CHARSET is also registered as the value of the default language identification register, and a predetermined value such as English can be set as the value of DEFAULT_CHARSET. The default value of DEFAULT_CHARSET can be set as appropriate for a specific application.

  When the client connects to the database, the client can issue commands. In this embodiment, the command is configured as an SQL statement. The command processing unit 118 receives a command issued from the client, and requests the processing unit in charge of processing according to the type of command.

  The command can include the language to be processed as a language identification value. When the language identification value of the language for which processing is requested is included, the information processing apparatus 110 performs processing for the specified language. . If the language identification value for specifying the process is not included, the CHARSET value of the language identification register 120b is used as the language identification value, and the process for the language is performed.

  The language identification register 120b is secured in a memory area managed by the information processing apparatus 110, and provides a function for identifying a language environment. The language identification register 120b can be configured in the information processing apparatus 110 in various mounting formats. For example, in the case of DB2 (DB2 is a registered trademark of International Business Machines Corporation) as a relational translator base. Can be implemented by assigning a variable representing this value to a variable group called a special register.

  The language identification register 120b functions as a language setting unit of the present embodiment, and can appropriately change the setting by a command such as “SET DEFAULT_CHARSET 'fr'” in response to a request from a client or a system administrator, for example. .

  The client connected to the database sends the language identification value used by the client when connecting to the database. This is because the language information is obtained from the operating system used by the client, and the language information and Table 1 below are obtained. The correspondence relationship with the language identification value is stored in an appropriate non-volatile memory, and the corresponding language identification value is sent to the database. Alternatively, the client sends the language information to the server, and the server stores the correspondence between the language information and the language identification value in Table 1 below in an appropriate non-volatile memory, and acquires the corresponding language identification value. May be.

  The command processing unit 118 analyzes the received command and requests the table processing unit 124 or the language resource processing unit 126 to perform processing according to the type of command. For example, in this embodiment, if the received SQL command includes a SET CHARSET statement that is a command for specifying a language, the language identification value that is an argument of the SET statement is registered in the language setting unit 120 in the CHARSET. To ask. On the other hand, when the command instructs an operation on the table, the table processing unit 124 is requested to perform the process. Further, if the command is an operation on the resource table, the language resource processing unit 126 is requested to perform processing.

  When the register processing unit 120a manages various variables held for each connected client and receives a “SET register name value” statement from the client, the register processing unit 120a changes the value of the specified register name in the language identification register 120b to the specified value. change.

  The table processing unit 124 accepts a table creation / change / removal command, a data insertion / update / deletion / query command, and the like from the client. The table processing unit 124 implements an extension command that enables the functions implemented in the present embodiment to be used. More specifically, the table processing unit 124 can include a table creation / update / removal unit 124a, a data insertion unit 124c, a data update unit 124b, and a data deletion unit 124d. The table processing unit 124 is implemented including a data inquiry unit 124e, and enables a table including the resource column of the present embodiment stored in the table storage unit 130 to be searched. Inquiries can also be made by applying a SELECT command of an SQL statement in this embodiment.

  The table processing unit 124 calls each processing unit, corrects the data in the resource column and resource table implemented in the present embodiment, and the data editing process and the data query process executed by the table processing unit 124 -It can be implemented using conventional functions, except that it allows editing and query processing for columns and resource tables.

  In the extended command, for example, the table creation command can be implemented by including the code that specifies the resource column implemented in the present embodiment as the column, and each process is performed in the resource column. Perform table creation / update / removal and data query on the described multilingual data. The resource column means a column including data expressed in multiple languages, which is implemented in the present embodiment. Resource columns manage values in multiple languages. In the present embodiment, values in a plurality of languages are managed using XML, and an XML parser implemented including DOM or SAX can be included. The use of XML as a structured language is a specific embodiment, and structured documents may be managed in any form.

  The language resource processing unit 126 receives, from a client, a resource table creation / removal command implemented in this patent, a data insertion / update / deletion command for the resource table, and the like. For this purpose, the language resource processing unit 126, in more detail, includes a resource table creation / removal unit 126a, a resource / data insertion unit 126c, a resource / data update unit 126b, and a resource / data deletion unit 126d. Can be configured.

  The table creation / modification / removal unit 126a executes processing for creating a table that holds resource columns and adding a resource column to the table. The data insertion unit 126c, the data update unit 126b, and the data deletion unit 126d respectively execute data insertion, data update, and data deletion in a plurality of languages in the resource column.

  The function of each processing unit will be described in more detail. The resource table creation / removal unit 126a creates or removes a resource table for holding values in multiple languages independently of the resource column. be able to. This resource table can be referenced from the resource column. Each resource table can be identified by a category name, and the category name can be specified in the definition of the resource column, thereby associating the resource column with the resource table.

  More specifically, the data insertion unit 126c executes a process of inserting a language value in the resource column. If the language identification value of the data added at this time is the same as the language identification register DEFAULT_CHARSET, the data is also stored as a default value. In addition, the data update unit 126b performs processing for inserting, changing, and deleting a language value in the resource column. If the language identification value of the added data is the same as the language identification register DEFAULT_CHARSET, the default value is processed in the same way.

  The data deletion unit 126d performs processing for deleting a record including the data in the resource column. The resource data insertion unit executes processing for adding data to be inserted to an appropriate area of the resource table. If the language identification value of the added data is the same as the language identification register DEFAULT_CHARSET, the data is stored as a default value.

  FIG. 1 shows a data structure 140 of the language identification register 120b set by the register processing unit 120a. In the language identification register 120b, an address area 142 for a default language identification register for setting a language identification value for specifying a default language to be used when there is no language value requested by the client, and a default requested by the client. And an address area 144 for a language identification register for registering the language identification value.

  In a specific embodiment, the address area 142 is referred to as registering the value DEFAULT_CHARSET as the default language identification register, and the language used by the information processing apparatus 110 in the default setting is the initial setting when the information processing apparatus 110 is started up. Etc. are set. In the present embodiment, the default language can also be changed based on, for example, a command from the administrator. The address area 144 is referred to as a language identification register for registering the value CHARSET, and the language of the operating system of the connected client is initialized. These language identification registers are held for each connected client, can be changed by issuing a SET statement from the connected client, and are released when disconnected.

  Each command can include a language identification value. When a language identification value is specified in the command, processing of the command is processed in the language environment of the specified language identification value. If not specified, it is processed in the language environment of CHARSET. The value of CHARSET can be changed by an explicit language setting command “SET CHARSET‘ CHARSET name ’” from the client.

  The resource data update unit 126b causes the resource table to execute processing for updating data already registered, and the resource data deletion unit 126d causes the data table registered in the resource table to be deleted. The resource table means a table structure for storing multilingual resource data according to this embodiment, and can be referenced from a plurality of resource columns. The resource column can be configured as a table together with a column having other attributes as a column of a specific table, and the resource table can be referred to. In other embodiments, the resource column can be referred to as the resource column. Multilingual resource data can also be stored.

  The resource column definition (definition information such as category name) processed by the table processing unit 124 and its data are stored in the table storage unit 130 and accessed from the table processing unit 124.

  The resource table definition processed by the language resource processing unit 126 (definition information such as category name) and its data are stored in the resource information storage unit 132 and accessed from the language resource processing unit 126. When the resource column with a category name is processed in the table processing unit 124, the value of each language is stored in the resource table of the category in the resource information storage unit, so that it can also be accessed from the table processing unit 124. Has been.

  The resource reference information storage unit of the language resource table storage unit 132 stores which column of which table uses which category of resource table, and the table processing unit creates, changes, and removes the table. If a resource column with a category name is defined at the time, the information in the resource reference information storage unit is updated based on the information. In addition, the information processing apparatus 100 shown in the figure is provided with another processing unit 128 for executing existing RDB processing related to other SQL commands.

  FIG. 2 shows an embodiment of a sequence from when the client connects to the information processing apparatus 110 according to this embodiment to when the connection is disconnected. The information processing apparatus 110 issues a command “db_start” 210 or the like at the same time as the activation thereof, activates the RDB, receives an RDB end command 220, and receives an access request from the client until the RDB processing of the information processing apparatus 110 is completed. Process. For example, when the client 1 connects to a database managed by the information processing apparatus 110, the language identification value transmitted from the client 1 at the time of connection is set to the value CHARSET of the language identification register. The default language identification register value DEFAULT_CHARSET is set to a preset value, for example, English. These registers are maintained for each connected client and provide a language environment for each client.

  The information processing apparatus 110 receives a connection request and a command (SQL sentence) 240 from the client 2 while processing an access request from the client 1. When the command includes a SET statement, the register processing unit 120a is requested to perform the processing. After the processing is completed, the processing result is returned to the client 240 and the next command is accepted. Similar connection processing and command requests are performed from the client 3 and the client 4, and the information processing apparatus 110 executes a service corresponding to the processing for each client.

  If the commands 230 to 260 are operations on the table, the table processing unit 124 is requested to perform the processing. After the processing is completed, the processing result is returned to the client, and the next command is accepted. Further, if the command is an operation on the resource table, the language resource processing unit is requested to perform processing, and after the processing is completed, the processing result is returned to the client and the next command is accepted. If the command received from the client is disconnected, the connection information with the client is discarded, the process is returned to the client, and the session with the client is terminated. When an existing command other than the command employed in this embodiment is received, the conventional processing is performed, and after the processing is completed, the processing result is returned to the client and the next command is accepted.

  FIG. 3 is a schematic flowchart of processing from when the information processing apparatus 110 and the client start a session until the client ends. The processing in FIG. 3 starts from step S300. In step S301, the client language sent at the time of the connection request is set to the value of CHARSET, and DEFAULT_CHARSET is set in the information processing apparatus 110 in the embodiment to be described. The language identification value “en” that specifies English, which is the default language environment, is set.

  In step S302, a command from the client is received. In step S303, it is determined whether a SET command and its argument are received as a command. If it is determined that a SET command has been received (yes), the process is performed in step S307. Then, processing is requested to the language setting unit 120, the register processing unit 120a and the language identification register 120b are called, and the value of CHARSET set as an argument of the SET command is set in the language identification register 120b. If it is determined in step S303 that a SET command has not been received (no), it is determined in step S304 whether or not the command is for commanding an operation on the table, and if the command is for commanding an operation on the table. (Yes) The table processing unit 124 is activated in step S308 to execute processing.

  If it is determined in step S304 that an operation for the table is not instructed (no), it is determined in step S305 whether the operation is for the resource table. If it is determined in step S305 that an operation for the resource table is requested (yes), the language resource processing unit is activated in step S309 to execute the process. On the other hand, if it is determined in step S305 that an operation for the resource table is not instructed (no), it is determined in step S306 whether the command is a disconnection request, and if it is not a disconnection request ( no), the conventional RDB processing is executed in step S310.

  If it is determined in step S306 that the request is to be disconnected (yes), the session between the clients is disconnected in step S311 and the process is terminated. In addition, after the processing of steps S307, S308, S309, and step S310 is completed, the information processing apparatus 110 returns the processing to step S302 and receives a request for a new command from the client.

  FIG. 4 shows a detailed flowchart of the resource creation process called in step S305 of FIG. 3 when it is determined that the command is a command for instructing the process for the resource table to be implemented in the present embodiment. The process of FIG. 4 starts from step S400, and in step S401, it is determined whether the received command is a command for creating a resource table, and it is determined that the command is a command for creating a resource table. (Yes) In step S406, the process of FIG. 6 is called to execute the process, and after the process, the process corresponding to the command is ended in step S411.

  When it is determined in step S401 that the resource table creation is not instructed (no), in step S402, it is determined whether or not the resource table deletion is instructed, and when it is determined that the resource table is deleted (yes) In step S407, if there is a column that refers to the specified resource table, an error is returned. If not, the resource table is removed, and the process ends in step S411. The deletion of the resource table can be instructed by the following formula (1), for example.

  If it is determined in step S402 that the command is not a command to delete a resource table (no), it is determined in step S403 whether the command is a command to insert a resource, and if it is determined to be a resource insertion ( yes), the process of FIG. 8 is started in step S408, the resource is inserted, and the process is terminated in step S411.

  In step S403, when it is determined that the resource is not inserted (no), in step S404, it is determined whether the command is for commanding resource update, and when it is determined that the command is for commanding resource update (yes), In step S409, the process of FIG. 11 is started. After the process, the process ends in step S411. Further, if it is determined in step S405 that resource deletion is requested (yes), the processing of FIG. 12 is started in step S410, resource data deletion is executed, and resource data deletion processing is not executed in step S405. (No) In step S411, the processing request to the resource table is terminated.

  FIG. 5 is a detailed flowchart of the process called in step S304 of FIG. 3 executed by the table processing unit 124 that executes the process on the table in this embodiment. The process in FIG. 5 starts from step S500. In step S501, it is determined whether the received command instructs to create a table. If it is determined that the command is a command to create a table (yes), In step S508, the process of FIG. 7 is called to execute the process, and in step S516, the process corresponding to the command is terminated.

  If it is determined in step S501 that the resource table creation is not instructed (no), it is determined in step S502 whether or not a table change is instructed. If it is determined that the table is changed (yes), step S509 is performed. Change the table with. In addition, when adding a resource column by changing the table, the same processing as the creation of the table is performed. In the table change process, the process of adding a resource column can be performed in the same manner as adding a column of another data type, and includes the code that specifies the resource process to be introduced in the present embodiment. It can be executed using the command of equation (2).

  If it is determined in step S502 that the table is not changed (no), it is determined in step S503 whether it is a command for instructing table removal. If it is determined to instruct for table removal (yes), the table is updated in step S510. Remove. When the category-attached resource column is defined, the keys of all records are checked in order, the reference counter of the corresponding record of the resource corresponding to the key is decremented by 1, and the process is branched to step S516. End the process.

  If it is determined in step S503 that the table is not removed (no), it is determined in step S504 whether it is a command for instructing resource insertion, and if it is determined to instruct to insert a resource (yes), in step S512, 14 and 15 are activated, data is inserted into the corresponding table, and after the data insertion process, the process is terminated in step SS516. If it is determined in step S504 that the command is not a command to insert data (no), it is determined in step S505 whether the command is a command to update data, and if it is determined to be data update (yes). 16 and 17 are started in step S513, the data update process is executed, and after the update process ends, the process ends in step S516.

  If it is determined in step S505 that the data is not updated (no), it is determined in step S506 whether the command is for commanding data deletion. If it is determined that the command is for commanding data deletion (yes), In step S514, the processing shown in FIGS. 18 and 19 is started to execute data deletion. After the processing, the processing ends in step S516. Further, in step S507, it is determined whether or not the command instructs the search. If it is determined that the data search is requested (yes), the data search is executed in step S515, and then the process is performed in step S516. End. The data search will be described in detail later. If it is determined in step S507 that it is not search processing (no), the processing request to the resource table is terminated in step S516.

  FIG. 6 is a flowchart of a schematic process when creating a resource table in the present embodiment. The process in FIG. 6 starts from step S600, and in step S601, a command for instructing creation of resource data is received. In step S602, a resource storage area is secured for storing XML that supports multiple languages, and in step S603, the process ends. The resource storage area is reserved so that language resource information can be stored and searched, and may be stored using a conventional database table function. A specific schema of the database may be used for this purpose, and the table name may be used as the resource category name. Hereinafter, a case where the schema name is RESOURCE, the table name is a category name, and language resource information is held in a column RES that holds one XML data type as a table column will be described. The creation of the resource table can be commanded by the following formula (3), for example.

  FIG. 7 shows a detailed flowchart of the table creation process executed by the information processing apparatus 110 in step S508 of FIG. The process in FIG. 7 starts from step S700, and in step S701, a command for instructing table creation is received. In step S702, the first definition of the target column is checked, and in step S703, it is determined whether or not the command instructs creation of a table in the resource column for the column.

  In the present embodiment, when creating a script that uses an SQL statement, a script for creating a table that holds resource columns can be described by the following expressions (4) and (5).

  The above formula (4A) is an embodiment in which the resource is shared with other tables and is managed separately from the table, and 'MTH' is a category name for identifying the resource. When resources are managed separately, a resource storage area and its data can be secured in advance by specifying the category name of the resource table, as shown in the following formula (5). Further, which column of which table refers to a separately managed resource is stored and stored in the reference information storage unit. This may be retained using the database table function. A case will be described below where the table schema name is RESREF, the table name is REFERENCE, and resource reference information is held in a column REF that holds one XML data type as a table column. Hereinafter, the table T1 will be described assuming that it is a resource table that registers the name of the calendar month and the number of days in the calendar month corresponding to multiple languages.

  If it is determined in step S703 that the column to be created is not a resource column but an instruction to create a column of a conventional data type (no), in step S704, the column information is stored using the conventional method. If storage and data storage areas are secured, it is determined in step S706 whether all column definitions have been checked, and if it is determined in step S706 that the processing of the column to be created has been completed (yes), step In S712, the process is terminated. If it is determined in step S706 that there is a column to be inspected (no), the next column is inspected in step S705, and the determination in step S703 is continued again until there is no target column.

  On the other hand, if it is determined in step S703 that the command is a command for creating a resource column (yes), in step S707, a category name is held as column definition information in addition to the conventional column definition information. If there is no category name, set the category name to NULL. In step S708, a column data (XML) storage area is secured. If a significant value is set for the category name in step S709 (yes), a resource of the category name has already been created in step S710. If NULL that is not a significant value is registered (no), the process branches to step S706 to determine whether or not a column to be processed remains. I do.

  On the other hand, if a resource has already been created for the category name in step S710 (yes), in step S709, it is determined whether or not a column to be further processed is left. Finish table creation or continue further inspection. If the category resource has not been created in step S710 (no), the category resource table is created in step S711, the data (XML) storage area is secured, and the process branches to step S706. And repeat the process.

  FIG. 8 shows a detailed flowchart of the process of step S408 in FIG. The data to be inserted can specify a resource value and a key for identifying the value. The process of FIG. 8 is a process executed by the resource / data insertion unit of the language resource processing unit 126. The processing in FIG. 8 starts from step S800 and is activated upon receipt of a command for instructing insertion of a structured document into the resource table. In step S801, each value (resource name, key name, Gets the value language identification value (if specified), if not specified, uses the value of CHARSET set in the language identification register.The command to add a structured document takes various forms Although it can employ | adopt, in the specific aspect in this embodiment, a command can be defined as following formula (6).

In the above formula (6), MTH following RESOURCE represents the category name of the resource, data “Jan” in the first column is a key, and data “January” in the second column represents a value. The key is used to identify values within the same category. In step S801, CHARSET
'Language identification value' can be omitted as an option. If omitted, the value of CHARSET in the language identification register 122 is used as the language identification value. The language identification value is a code that specifies the language environment requested by the access request.

  In step S802, it is determined whether the key is already registered in the resource table. If it is determined in step S802 that the key is not already registered (no), in step S803, the key and data with the specified language identification value are inserted into the resource table. At this time, if the language identification value is the same as DEFAULT_CHARSET set in the default language identification register, data is also registered as the default value.

  On the other hand, if it is determined in step S802 that the key is already registered (yes), the process branches to step S804 to determine whether data corresponding to the language designation value is defined. If it is determined in step S804 that the data has already been registered (yes), an error message is issued to notify the client that the data in the corresponding language is already registered in step S806, and the process is performed in step S807. finish. If no data corresponding to the language designation value is registered in step S804 (no), data is registered with the designated language identification value as a child element of the corresponding record in step S805. Further, if the language identification value is the same as DEFAULT_CHARSET set in the default language identification register, the data is registered as the default value, and the process returns to step S807 to end.

  FIG. 9 shows an embodiment of a data structure inserted into the resource table according to this embodiment. As shown in the data structure 910, the resource column of each record is identified by a value tag for each data corresponding to a language environment difference, and one record holds information about one key, It is identified by the key attribute and registered to give a hierarchical structure. Further, as shown in the data structure 910, the language identification value designated by the client is set as charset = charset name (default value is default) (the language identification value is set in the charset name). The added resource data is added as a child node 912 in the node of the structured document 910 specified by the <resource> tag. The value refcount is a reference counter and corresponds to the number of data in the column of the table that refers to the corresponding key of the resource table. The reference counter value setting process will be described in more detail later.

  In this embodiment, as shown in FIG. 9, the value to be managed by the structured document is not a simple value such as month, but for example, as a column of the table T2, NAME VARCHAR (10), DESCRIPTION RESOURCE (' When defining DESC '), “IBM” can be registered in the NAME column, and “IBM stands for International Business Machines” can be registered in the DESCRIPTION resource column for English and default.

  The corresponding Japanese data of DESCRIPTION can be registered as a child element by updating the table or inserting the resource into the corresponding category, such as “IBM is an abbreviation for International Business Machines”. . In yet another embodiment, in addition to DESCRIPTION, for example, blog content, or other data to be provided as web content, the same translated value or translated sentence is registered in the same record. Multilingual support is possible.

FIG. 10 shows a flowchart of update processing of data registered in the resource table of this embodiment. The process of updating the data registered in the resource table is a process performed using the “UPDATE RESOURCE] script. The process in FIG. 10 is an UPDATE command for updating the structured document in the resource table from the client.
By receiving the RESOURCE statement, the resource / data update unit 126b is called and started in step S1000. In the embodiment to be described, the command for instructing update is for instructing rewriting of the value, and can be given by the following equation (7).

  In step S1001, each value (resource name, key name, value, and language identification value (if specified) described in the script is acquired. CHARSET 'language identification value' can be omitted. The value of CHARSET in the identification register 120b is used as the language identification value, and in step S1002, data matching the key value and the language identification value is searched for, in step S1003, it is determined whether or not the corresponding data exists, If the corresponding data does not exist (no), an error is returned to the client 230 in step S1005, and the process is terminated in step S1006.

  On the other hand, if it is determined in step S1003 that the corresponding data exists (yes), the value of the corresponding data is rewritten with the data specified by the command in step S1004. If the value after rewriting is NULL, the corresponding data is deleted. If the language identification value matches the value of DEFAULT_CHARSET in the default language identification register, the default value is also updated, and the process ends in step S1006. With the processing in FIG. 10, once created data can be rewritten in response to a command from the client, and unnecessary data can be deleted, values can be updated, and the like.

  FIG. 11 is a diagram for explaining the rewrite processing embodiment 1110 according to this embodiment using data described in a script and a structured document. The script 1111 for instructing rewriting sent from the client 230 is “UPDATE RESOURCE category name SET VALUE =‘ value ’WHERE KEY =‘ key ’CHARSET’ language identification value ’”. When the command sent from the client starts with “UPDATE RESOURCE”, it is determined that rewriting of the value of the resource column is instructed, and the rewriting process is started.

More specifically, in order to rewrite the existing data 1130, the script 1120 for instructing rewriting is “UPDATE”
It is assumed that RESOURCE MTH SET VALUE = '睦 月' WHERE KEY = 'Jan'CHARSET'ja' is received. First, the information processing apparatus 111 collates the category name MTH, the key value, and the language identification value, acquires the corresponding data 1130, and sets the corresponding value of the data 1130 as “value = 睦 月” specified by the script 1120. It is registered as data 1140 rewritten to “Yutsuki”.

  FIG. 12 shows a flowchart of processing for deleting data registered in the resource table of this embodiment. The deletion process of data registered in the resource table is a process performed when a command starting with “DELETE FROM RESOURCE” is received in this embodiment. The process of FIG. 12 is called by the resource / data deletion unit 126 in step S1200 upon receiving a DELETE FROM RESOURCE statement from the client, and starts the process. In this embodiment, a command for instructing deletion of a structured document in the resource table and its argument can be given by a command of the following formula (8).

  In step S1201, each value (resource name, key name, value, and language identification value (if specified) described in the script is acquired. CHARSET 'language identification value' can be omitted. The value of CHARSET in the identification register 120b is used as a language identification value In step S1202, the corresponding data is acquired, and if it is determined in step S1203 that the corresponding data does not exist (no), in step S1204, the client is notified. An error is returned, and the process ends in step S1208.

  On the other hand, if it is determined in step S1203 that the corresponding data exists (yes), it is checked in step S1205 whether the value of the reference counter is 0. If the reference counter is 0, the corresponding data is determined in step S1206. Delete all values in key units. After deletion, the result is returned to the client, and the process ends in step S1208. If the reference counter is not 0 (no), an error is returned to the client in step S1207, and the process is terminated in step S1208. The processing shown in FIG. 12 makes it possible to delete data once created in response to a command from the client.

  Next, the command for removing the resource table can be implemented as the following equation (9).

  To delete a resource table, refer to the resource reference information and return an error if there is a column referring to the specified resource table. On the other hand, if there is no column that refers to the specified resource table, it can be executed by removing the resource table.

  In the above, the creation of the table holding the resource column, the creation, insertion, update, and deletion processing of the resource table have been described. Hereinafter, a process for inserting, updating, and deleting data and a process for referring to various data will be described with respect to a table holding resource columns.

  FIG. 13 is a flowchart of processing executed by the data insertion unit 124c that inserts data into a table holding resource columns in the information processing apparatus 110 according to the present embodiment. The command can take various forms, but in a specific form in the present embodiment, the command can be defined as the following formula (10).

Expression (10) above shows an example of changing the Syntax. The CHARSET 'language identification value' can be omitted, and if omitted, the value of CHARSET in the language identification register 120b is used as the language identification value. As shown in Expression (10), as a method for inserting data in the resource column, functions such as RESOURCE_SET () and RESOURCE_REF () can be used in addition to specifying the value itself. The command “RESOURCE_SET ()” can set a key name as a first argument and a value as a second argument, and data is saved based on each argument. The command “RESOURCE_REF ()” can set a key name in the first argument and means to refer to the value of the key. The key value is the INSERT
It can be inserted in advance with the INTO RESOURCE statement, and RESOURCE_REF () can be used to refer to the value.

  In step S1300, the resource data insertion process is started by receiving a command for instructing insertion and calling the resource data insertion unit 126c. In step S1301, the table name, the data of each column, and the language identification value (if set) set in the command are acquired. In step S1302, the definition and value of the first column are extracted.

  As described above, CHARSET 'language identification value' can be omitted as an option. When omitted, the value of CHARSET in the language identification register 120b is used as the language identification value. The data of each column is processed from the first column. In step S1303, it is determined whether or not the processing target column is a resource column. If the processing target column is not a resource column (no), in step S1304, a table processing unit that executes conventional processing is called. A process for the table is executed using the existing process, and it is determined in step S1307 whether there is a column to be further processed. If it is determined in step S1307 that there is a column to be further processed (yes), the process returns to step S1303 and the determination is repeated again. If no column to be processed remains in step S1307 (no), the process ends in step S1307.

  If it is determined in step S1303 that the processing target column is a resource column (yes), it is determined in step S1305 whether the category designation value is NULL. If the category specification value is NULL in step S1305 (yes), a structured document that gives a language resource to the corresponding column is described in step S1306. When the language identification value matches the value of the default language identification register, the default language value is also inserted. On the other hand, if the category name is not NULL (no), the process branches from point A to the process of FIG.

  The process of FIG. 14 is started by passing control from the process of FIG. 13 at point A. In step S1401, a category name is acquired, and in step S1402, it is determined whether only a value is specified. Is designated (yes), a key is automatically generated in step S1403, and an unregistered key is obtained. In step S1404, the same processing as described in the above equation (8) is performed. At this time, the reference counter of the key of the corresponding resource is set to 1. On the other hand, if it is determined in step S1402 that RESOURCE_SET () is used in the command and a value other than the key is included in step S1406 (no), the key name and value are acquired, and in step S1407 It is determined whether or not the key corresponding to the resource of the category to be registered has already been registered. If the key has already been registered (yes), an error is returned in step S1410 and the process is terminated.

  On the other hand, if no key is registered in step S1407 (no), the process returns to step S1404 to repeat the process.

  If it is determined in step S1406 that RESOURCE_SET () is not included (no), it is determined in step S1408 whether the command includes a command for changing the reference counter, for example, RESOURCE_REF (). To do. If it is determined in step S1408 that there is a command for correcting the reference counter (refcount) (yes), it is determined whether a key is already registered in the resource table in step S1409. If it is not registered (no) In step S1410, an error is returned assuming that the corresponding key does not exist. On the other hand, if the key exists (yes), in step S1411, the reference counter of the corresponding key is incremented by 1, and the process returns to step S1412.

  FIG. 15 is a flowchart of processing of the resource / data update unit 126b that updates the data registered in the table holding the resource column in the information processing apparatus 110 according to the present embodiment. The process of FIG. 15 is started by receiving and calling a command for updating in step S1500, and acquires the language identification value specified in the command in step S1501. The language identification value can be omitted. If omitted, the value of CHARSET in the language identification register 120b is used as the language identification value. In step S1502, the column name and value of the first condition described in the WHERE clause are acquired, and in step S1503, it is checked whether a resource column is specified. If it is determined in step S1503 that the resource column name is not specified (no), a record to be updated is acquired using conventional processing in step S1504.

  On the other hand, if it is determined in step S1503 that a resource column is specified (yes), in step S1507, it is checked whether the category name of the resource data is NULL. If it is NULL (yes), step In step S1508, records in the corresponding column of the corresponding record are obtained in order. Thereafter, in step S1509, a language identification value corresponding to the CHARSET name is acquired. If there is no corresponding value, the default value is obtained. In step S1510, the condition is determined using the acquired value. If the acquired value matches the value specified in the condition, the update or insertion target is set, and the process branches to step S1505. .

  If it is determined in step S1507 that it is not NULL (no), the corresponding data in the corresponding resource table is obtained from the key name stored in the corresponding column in step S1511, and the corresponding data is determined in step S1512. Refer to the resource information of the category and obtain the key and the value corresponding to the CHARSET name. If not, get the default value. In step S1513, the acquired value is used to determine the condition. If the acquired value matches the value specified in the condition, the update or insertion target is set, and the process branches to step S1505.

  In step S1505, it is determined whether there is a condition following the WHERE clause. If there is a condition (yes), the next condition described in the WHERE clause is acquired in step S1506, and the process branches to step S1503. And repeat the process. On the other hand, in step S1505, it is determined whether there is a condition following the WHERE clause. If it is determined that there is no condition (no), the process of FIG.

  FIG. 16 shows a flowchart of processing subsequent to the insertion processing of FIG. The process of FIG. 16 is started at the point C in FIG. In step S1600, the update target record is set as a processing target, and in step S1601, the first column name and value specified by the command instructing the update are acquired. In step S1602, it is determined by referring to the resource information whether or not the column currently being determined is a resource column. If the column is not a resource column (no), in step S1603, conventional processing is applied to the column. Update to.

  On the other hand, if it is determined in step S1602 that the column is a resource column (yes), it is determined in step S1604 whether the category of the resource is NULL. If it is NULL (yes), in step S1605, If the value of the language identification value of the corresponding column exists, the value is replaced. If not, insert it. If the value after replacement is NULL, the language identification value is deleted. If the language identification value is the same as the value of DEFAULT_CHARSET in the default language identification register, the default value is also replaced.

  If the determination in step S1604 is not NULL (no), in step S1606, the corresponding data in the corresponding resource table is obtained from the key stored in the corresponding column of the corresponding table. In step S1607, the language identification value is If a value exists, replace that value. If not, insert it. If the value after replacement is NULL, the language identification value is deleted. If the language identification value is the same as the value of DEFAULT_CHARSET in the default language identification register, the default value is also replaced, and the process branches to step S1608.

  In step S1608, it is determined whether the next column to be updated remains. If no column remains (no), the process ends in step S1610. On the other hand, if it remains, in step S1609, the next column name and value to be updated are acquired, the process is branched to step S1602, and the process is repeated.

  FIG. 17 is a flowchart of processing for deleting data registered in a table holding resource columns in this embodiment. The processing in FIG. 17 is the same as the processing in FIG. 15 except that the update is replaced with deletion, and the column check is performed, so detailed description will not be given. In the process of FIG. 17, when the point C is reached, the control is transferred to the process of FIG. 18 and the substantive process of deletion is started.

  FIG. 18 is a flowchart of the deletion process subsequent to FIG. The process shown in FIG. 18 starts at point C with control given from the process shown in FIG. 17. In step S1800, the deletion target record is set as a deletion target, and in step S1801, the first column is checked. In step S1802, it is determined whether or not the column is a resource column. If the column is not a resource column (no), it is determined in step S1806 whether or not a column to be further processed remains. (Yes) In step S1809, the next column is checked and the process is repeated. On the other hand, if it is determined in step S1806 that the next column does not remain (no), in step S1808, the conventional data deletion unit 124d is called to delete the column by applying conventional processing, and in step S1810. End the process.

  If it is determined in step S1802 that it is a resource column (yes), it is determined in step S1803 whether the category of the resource is NULL. If it is NULL (yes), the process branches to step S1806. Further, it is determined whether there is a column to be further processed, and the processing is repeated. On the other hand, if it is determined in step S1803 that the category of the resource is not NULL (no), a key stored in the corresponding column of the corresponding table is obtained in step S1804, and the corresponding category is determined in step S1805. The key reference counter value is decremented by 1, the process is branched to step S1806, the process is repeated, and the process for the target column is completed. Then, the process ends in step S1810.

  FIG. 19 shows an embodiment of a table with resource columns generated according to this embodiment. The data structure shown in FIG. 19 shows a T1 table 1900 that holds a RESOURCE data type column MONTH and an INTEGER data type column NUM_OF_DAYS, and a resource information table 1930 that defines a column MONTH attribute of the table 1900. Yes. In the embodiment to be described, the resource column 1910 is a resource column that stores a structured document describing data of a RESOURCE data type in which the column name = MONTH has no category name.

  In the embodiment to be described, the column 1920 with column name = NUM_OF_DAYS is a conventional column for registering a value whose data type is INTEGER, and is a column for registering the number of the last day of a calendar month. The data in the resource column is described in XML starting with the tag <value> in the range identified by the tag <resource>.

  When a data acquisition request for “MONTH” of the table represented by the resource table 1900 is received from the client by a SELECT statement or the like, if a language identification value is set in the SELECT statement, that value is used. A value corresponding to the language identification value is acquired from the resource column 1910 using the value of CHARSET in the language identification register as the language identification value. If there is no value corresponding to the language identification value, a value stored as a default is acquired.

  Further, the definition information 1930 of the column MONTH of the table T1 is created simultaneously with the creation of the table 1900 as the column information of the table 1900, and the category name is added to the information held conventionally. For the column NUM_OF_DAYS of the table T1, definition information is created as before. Necessary information is registered in the resource column as a column attribute of the table 1900, and data management of the resource column of the table 1900 is enabled. In the embodiment shown in FIG. 19, the resource table 1900 does not have a category name. Therefore, the resource column storage area is used as it is to store language resources. In the embodiment shown in FIG. 19, the key value is not registered, and a structured document to be added to an appropriate record is added by using the matching of the value set directly in value.

  In the structured document registered in the resource table 1900, a time stamp of the time of creation and editing is registered so that the history of data creation / editing can be traced. Each time stamp is used by a database system administrator to check the data change history and detect whether, for example, the default or English values have been updated and other language values have been updated. Is done.

  FIG. 20 shows a case where category name = MTH is specified as column information of the RESOURCE data type when creating a table in this embodiment. The data structure shown in FIG. 20 includes a table information 2030 of T1 that holds a column MONTH of RESOURCE data type and a column NUM_OF_DAYS of INTEGER data type, and a resource information table 2020 that defines attributes of the column MONTH of table information 2030. , A resource table 2000 of category MTH is shown. In the embodiment of FIG. 21, the resource column MONTH itself does not hold a language resource but holds a key. The value corresponding to the key is held together with the key in the column 2010 by the resource table 2000 for that category.

  When a data acquisition request for “MONTH” of a table represented by 2030 is received from the client 230, such as a SELECT statement, the language identification value is set in the SELECT statement, and if not, the language identification value is used. Using the value of CHARSET in the identification register as the language identification value, data corresponding to the key stored in the MONTH save area is detected from the resource table of the corresponding category, and the value corresponding to the language identification value is obtained. To do. If there is no value corresponding to the language identification value, the value stored as default is acquired.

  FIG. 21 shows an embodiment of a resource reference table 2100 that stores resource reference information indicating that the table holding the resource column is referring to the resource table in the present embodiment. The resource reference table 2100 is a table that holds information that associates a schema name, a table name, and a column name with a category name when a resource column is defined with a category name. A data structure to be stored. In the embodiment shown in FIG. 21, in the REF column of the resource reference table 2100, a schema name, a table name, and a column name referring to the category are registered as a structured document <reference category = “MTH”>. Has been. Further, it is shown that the CITY category is referenced from the “CITY” column of the two tables “CUSTINFO” and “SHOPINFO”.

  A process for updating data using a resource column will be described. The SQL statement in this case can be implemented by adding the SQL statement CHARSET 'language identification value' for updating data. Specific embodiments will be described using the following formula (11).

  In the above formula (11), CHARSET 'language identification value' can be omitted as an option. When the CHARSET clause is omitted, the value of CHARSET in the language identification register 120b is used as the language identification value. The example of Expression (11) is an embodiment in which Italian (it) is designated as the language identification value. As shown in Expression (11), the data in the resource column can also be described as a structured document in the same format as the columns of other data types.

  12 to 18, when a resource column is specified in the WHERE clause, language identification value data is extracted and processed. If there is no language identification value data, default data is extracted and processed. If a resource column is specified in the SET clause, it is saved as language identification value data. If the language identification value data is already saved, it is replaced. If not, it is inserted. The storage and insertion methods are the same as the processing for inserting data into a table holding resource columns.

  If 'January' is registered as the default value of the MONTH value as the state before the update process of Expression (11) is performed, and the corresponding Italian language is not registered, the update process of Expression (11) Thus, Italian “Gennaio” is registered in the data corresponding to the default value “January” of the value set in MONTH. On the other hand, if the Italian value corresponding to the default value 'January' has already been registered as the value of MONTH, the record corresponding to MONTH = 'January' is not found in the update process of formula (11). Data is not updated.

  In addition, the SQL statement for deleting data using resource columns can be implemented by finding the corresponding record by the same process as updating.

  Similarly, in the case of Expression (12), the ‘language identification value’ of CHARSET can be omitted as an option. If omitted, the value of CHARSET in the language identification register 120 b is used as the language identification value. The example of Expression (12) illustrates the case where Japanese (ja) is specified as the language identification value. If a resource column is specified in the WHERE clause, language identification value data is fetched and processed. If there is no language identification value data, default data is extracted and processed. In the above formula (12), the record whose Japanese data of MONTH is “January” is deleted. If a resource column with a category name is defined in the column of the record to be deleted, the reference counter of the corresponding key of the resource of the category is decremented by one.

  The data inquiry process can be implemented using a SELECT statement or the like, and the process for the resource column can be implemented in the information processing apparatus 110 by the same process as the insertion / update / deletion process. The following formula (13) describes an embodiment of the SQL statement used in the query process.

  In the above formula (13), CHARSET 'language identification value' can be omitted as an option. When omitted, the value of CHARSET in the language identification register 120b is used as the language identification value. In the example of Expression (13b), description will be made assuming that Japanese language (ja) is designated as the language identification value. As shown in the expression (13b), the data in the resource column can be described in the same manner as other data type columns. The process of querying the data in the resource column can be executed by extracting data corresponding to the language identification value. In the example of the expression (13c), a SELECT statement that requests the value of the resource column can be described in the same way as other data type columns. When acquiring the value of the resource column, the value of the language identification value is acquired. If not, the default value is acquired.

  Hereinafter, an embodiment of search processing for the database system 100 of the present embodiment will be described. The search processing is executed by the data inquiry unit 124e shown in FIG. 1. For example, when SQL is used, the command processing unit 118 receives the SELECT statement and requests the data processing unit 124 to perform processing. It is executed by. The search result is generated as a table and returned to the client as a search result. The search process is a search corresponding to an access for the purpose of extracting the contents of the RDB for the purpose of maintaining the database by the RDB administrator in addition to accessing the information processing apparatus 110 by the client for the purpose of searching for information. Includes processing.

  Also in this embodiment, when querying data using a SELECT statement or the like, an SQL function referred to as a scalar function or a table function can be specified. A function module for executing a scalar function or a table function is registered in advance. When a scalar function or a table function registered by a SELECT statement is specified, the corresponding function module is called. The scalar function module returns a value as the processing result. The table function module returns table data (column name and zero or more records) as the processing result. The scalar function and the table function for calling the language resource handling processing in this embodiment are shown in Table 2 below, but are not limited to the following functions.

  FIG. 22 shows an embodiment of the data structure of the SELECT statement and the corresponding search result generated by the search processing of this embodiment. The data structure 2200 includes a SELECT statement including a scalar function for extracting the category name of the resource used by the column MONTH of the table T1 of the schema “xxx” and a key function held by the record, and a search result. The search result when extracted from the resource table 2030 of FIG. 20 is shown. The SELECT statement requests that the column MONTH category name, column MONTH key name, and column NUM_OF_DAYS value (number of days in the month) be extracted from the table T1, and each value is listed in the detection results. Is shown.

  In the embodiment shown in FIG. 22, in Table 2 shown in Table 2, the scalar function (1) that returns a category name returns the category name defined in the corresponding schema name, table name, and column name. If there is no category name, NULL is returned. Also, in Table 2, the scalar function that returns the key name of (2) also returns the key stored in the resource column data. If the category name is not used, the key is not used, so NULL is set. return. In the embodiment of FIG. 22, the table function 1 that returns the resource information of (3) in Table 2 returns the resource information of the corresponding category in a table format. In the embodiment of 2210 of FIG. Although the key, reference counter value, language, value, creation date, and last update date are returned, the present invention is not limited to the embodiment described.

  In Table 2, the processing of the table function 2 that returns the resource information of (4) will be described. The function 2 returns the resource information included in the corresponding resource column in a table format, and includes a schema name, a table name, and a column name. Are used as arguments, and in addition to the value of the table function 1 in Table 2, the key value and the category name are extracted. IDs are dynamically generated and used to correlate data stored in the same resource column. If there is no category name in the resource table, NULL values are returned for the category name, key name, and reference counter value.

  FIG. 23 shows an embodiment of a search result using the function (4) in Table 2 of this embodiment. The data structure 2300 shows the result when the SELECT statement including the table function for extracting the resource information of the column MONTH of the resource table T1 of the schema xxx and the search result are extracted from the table shown in FIG. The RESOURCE.RESOURCE_INFO ('schema_name', 'table_name', 'column_name') table function implemented in this embodiment includes the category name, key name, reference counter value, value language, value, creation date, and last update date. The result shows that the values for CATEGORY, KEY, REFCOUNT, CHARSET, VALUE, CREATED, and LASTMODIFIED columns are listed. In the SELECT statement shown in FIG. 23, resource information can be extracted from the column name of the table.

  Further, FIG. 23 shows a query result 2310 for a function that returns resource reference information (5) in Table 2, that is, a table function that returns which column of which table refers to which category of resource. An embodiment is shown. In the embodiment of the search result 2310, the introduction pair is an embodiment in which registered elements are extracted from the resource reference table 2100 of FIG.

  The search processing shown in FIG. 23 can also be performed for the purpose of acquiring data registered in the RDB by a client accessing the database. Further, the search process shown in FIG. 23 can be used by the RDB administrator for checking whether or not there is data associated between languages. As a result, the resource table can be maintained while considering the resource column being referenced.

  As shown in FIG. 22 and FIG. 23, in this embodiment, data expressed in multiple languages is managed in a single column, and records having the same meaning are stored in each language. Multilingual data can be managed efficiently without creating a plurality of files or dividing and managing a table.

  FIG. 24 shows another embodiment of the resource table of this embodiment. The embodiment shown in FIG. 24 corresponds to an embodiment in which employee information corresponding to a plurality of language notations is managed as a resource table. At the time of creating the database, only the resource reference table 2410 exists, and the entity content and resource table of the employee information table 2420 that holds the resource column corresponding to the subsequent input are created.

  As the columns of the employee information table, the employee name and work location are included, the employee name is the resource column without category, and the employee work location is the resource column 2430 with category name = CITY. If the resource table for the category CITY used in the column does not exist when creating the employee information table, the resource table is also created, and the work column of the employee information table is displayed in the resource reference table. Add information referring to the resource of category name CITY. In this case, the SQL statement for creating the employee information table is given by the following formula (14).

  Furthermore, in the embodiment of FIG. 24, a customer information table 2440 that refers to the resource table 2430 (category name = CITY) is created. In the embodiment of FIG. 24, as the column of the customer information table 2440, the residence RESIDENCE is defined as a resource column of category name = CITY. Since the resource table 2430 for CITY has already been created by the SQL statement (12), the column of the resource table can be referred to. In this case, information referring to a resource whose category column is CITY in the customer information table 2440 is added to the corresponding resource reference table. An exemplary SQL sentence in this case is given by the following formula (15), and a customer information table 2440 = SCHEMA.CUSTINFO is created.

  FIG. 25 shows a resource table 2500 that includes a name column defined as a resource column after several records have been inserted into the employee information table. For example, for the name = Taro Yamada, the default value, the English value, the German value, the Japanese value, the French value, and the Italian value are described as XML. Similarly, the value of name = Ichiro Sato is registered in the next record. Further, following the name column, data of other created columns is stored.

  The definition of the name column of the employee information table is managed in the same format as other columns like the data structure 2510, and NULL is set as the category name. Moreover, CITY is set as the category name in the definition of the work location column in the employee information table. The work column is a resource column with a category name, and the data structure in that case is shown in 2520. In a resource column with a category name, the key name is stored as the data, and the value is stored in the resource table of the category in association with the key. The definition of the residence column in the customer information table is set with CITY as the category name as in the data structure 2520. A data structure giving a reference structure in this case is shown in 2520.

  FIG. 26 shows the data structure of the resource table of category CITY. In the resource column 2600 of the category CITY, it is indicated that the value for the key name = Tokyo is defined in the first record of the resource table in default, English, German, Japanese, and French. In the residence column of the customer information table 2610, key names Osaka, Tokyo, and New York are registered.

  In the described embodiment, the reference counters of Tokyo and New York in the resource column of category CITY in the resource table 2600 indicate that reference is made from both the employee information table and the customer information table, and refcount = 2. On the other hand, the reference counter of the key name = Osaka is held at refcount = 1, and is set as the value of the refcount attribute. The data structure of the resource reference information table generated in the embodiment of FIG. The resource reference information table 2630 describes that the category CITY resource table 2600 refers to the EMPINFO WORKLOC column and the CUSTINFO RESIDENCE. Further, as shown in the data structure 2610, the keys can be cross-referenced with each other.

  As described above, by using the resource table, it is possible to refer to the same resource from a plurality of columns.

  As described above, according to the present invention, even in the case of data that needs to be supported in multiple languages, a plurality of records having the same meaning are created or the table is divided to hold the values of the respective languages. Multilingual data can be managed efficiently without having to manage them.

  The present invention provides, for example, a database for managing messages posted on an Internet bulletin board that can be attended by people all over the world, as well as contents of a web site adapted to the language environment of the client 230. The relational database such as the existing DB2 can be extended and implemented.

  Further, the function processing unit of the present invention is described as a specific embodiment for explaining the present invention, and each function corresponds to a specific mounting format, and any processing unit of the information processing apparatus It may be implemented as a function.

  The functions of this embodiment are described in an object-oriented programming language such as C ++, Java (registered trademark), Java (registered trademark) Beans, Java (registered trademark) Applet, Java (registered trademark) Script, Perl, and Ruby. The program can be realized by a program executable by the apparatus, and the program can be stored in a device-readable recording medium such as a hard disk device, CD-ROM, MO, flexible disk, EEPROM, EPROM, and distributed. It can be transmitted over the network in a possible format.

  Although the present embodiment has been described so far, the present invention is not limited to the above-described embodiment, and other embodiments, additions, changes, deletions, and the like can be conceived by those skilled in the art. It can be changed, and any aspect is within the scope of the present invention as long as the effects and effects of the present invention are exhibited.

Embodiment of the database system 100 of this embodiment. An embodiment of a sequence from when a client connects to the information processing apparatus 110 of this embodiment to when the connection is disconnected. 4 is a schematic flowchart of processing from when the information processing apparatus 110 and the client start and end a session. FIG. 4 is a detailed flowchart of processing in step S305 in FIG. 3 when it is determined that the command is a command for instructing processing for a resource table to be implemented in the present embodiment. FIG. 4 is a detailed flowchart of processing in step S304 in FIG. 3 executed by the table processing unit 124 that executes processing on a table in the present embodiment. FIG. 6 is a flowchart of a schematic process for creating a resource table executed by the language resource processing unit 126 in step S406 of FIG. 4 in the present embodiment. 6 is a flowchart of processing for creating a table executed by the table processing unit 124 in step S508 of FIG. 5 in the present embodiment. 5 is a detailed flowchart of the process in step S408 in FIG. Embodiment of a data structure inserted into a resource table according to this embodiment. 6 is a flowchart of update processing of data registered in the resource table of the embodiment. The figure explaining the update process of the data registered into the resource table of this embodiment using the data described by the script and the structured document. 6 is a flowchart of processing for deleting data registered in the resource table of the embodiment. 9 is a flowchart of processing for inserting data into a table holding resource columns in the information processing apparatus 110 according to the present embodiment. 14 is a flowchart of processing subsequent to the processing in FIG. 13. 9 is a flowchart of processing for updating data registered in a table holding resource columns in the information processing apparatus 110 according to the present embodiment. 16 is a flowchart of processing subsequent to the insertion processing in FIG. 10 is a flowchart of processing for deleting data registered in a table holding resource columns in the embodiment. FIG. 18 is a flowchart of a deletion process subsequent to FIG. Embodiment of the table which did not specify a category name as a resource column when creating a table in this embodiment. In this embodiment, when creating a table, an embodiment in which category name = MTH is specified as a resource column. Embodiment of the resource reference information table 2100 which shows that the table holding a resource column is referring to a resource table in this embodiment. An embodiment of a data structure of a SELECT statement and a corresponding search result generated by the search processing of this embodiment. Another embodiment of the search processing embodiment of the present embodiment. Other embodiment of the resource column and resource table of this embodiment. The figure which showed the data structure 2500 of the name column after some records were inserted in the employee information table. The figure which showed the data structure of the resource table which has a customer information table and the category CITY, and a resource reference information table. The figure which showed the data structure of the conventional database utilized for multilingual correspondence.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 ... Database system, 110 ... Information processing apparatus, 112 ... Network, 114 ... Network adapter, 116 ... Client connection processing part, 118 ... Command processing part, 120 ... Language setting part, 120a ... Register processing part, 120b ... Language Identification register 124... Table processing unit 126. Language resource processing unit 128. Other processing unit 130 130 Table storage unit 132 Language resource table storage unit

Claims (19)

An information processing apparatus that processes an access request from a client that uses a plurality of language environments, the information processing apparatus includes:
A resource table that stores multilingual resource data, and a resource table storage unit that stores a resource table that can be referred to from a column including multilingual data in the database;
A language setting unit for identifying a language environment of the client accessing the information processing apparatus and setting the language environment;
A client connection processing unit for setting a language identification value for designating a language environment of the client in the language setting unit;
A command processing unit that examines a command included in the access request and determines the presence of a command that requests an operation on the resource table ;
When the command processing unit determines that a command requesting an operation on the resource table is included, the command processing unit receives the command, and causes the resource table to be accessed by the language environment set in the language setting unit, An information processing apparatus comprising: a language resource processing unit that registers a plurality of structured documents including values described in different languages for the same value as a child node in a record for each same value in the resource table .   The language setting unit includes a default setting unit that registers a language environment used as a default setting by the information processing apparatus, and the client connection processing unit includes a language identification value included in an access request issued by the client during the session. The information processing apparatus according to claim 1, wherein priority is registered as a client language environment.   The information processing apparatus according to claim 2, wherein the client language environment is changed according to a language identification value included in the access request.   The information processing apparatus according to claim 3, wherein the information processing apparatus sets the client language environment as a language environment having priority over the default setting, and provides a different client language environment for each client.   The language resource processing unit is configured to execute insertion, update, and deletion of the structured document using the language environment set by the language setting unit, a resource data insertion unit, a resource data update unit, The information processing apparatus according to claim 4, further comprising a resource / data deletion unit. A database system that processes access requests from clients using multiple language environments, the database system comprising:
A resource table that stores multilingual resource data, and a resource table storage unit that stores a resource table that can be referred to from a column including multilingual data in the database;
A language setting unit for identifying a language environment of the client accessing the information processing apparatus and setting the language environment;
A client connection processing unit for setting a language identification value for designating a language environment of the client in the language setting unit;
A command processing unit that examines a command included in the access request and determines the presence of a command that requests an operation on the resource table ;
When the command processing unit determines that a command requesting an operation on the resource table is included, the command processing unit receives the command, and causes the resource table to be accessed by the language environment set in the language setting unit, A language resource processing unit that registers a plurality of structured documents including values described in different languages for the same value as a child node in a record for each same value in the resource table ;
The language setting unit includes a default setting unit that registers the language environment of the information processing apparatus as a default setting, and a client connection that registers a language identification value included in an access request issued by the client during the session as a client language environment. A database system including a processing unit.   The language setting unit includes a default setting unit that registers a language environment used as a default setting by the information processing apparatus, and the client connection processing unit includes a language identification value included in an access request issued by the client during the session. The database system according to claim 6, wherein priority is registered as a client language environment. The language resource processing unit is configured to execute insertion, update, and deletion of the structured document using the language environment set by the language setting unit, a resource data insertion unit, a resource data update unit, A resource data deletion unit, and the language resource processing unit accesses the resource table using the command when the command processing unit determines that the command requests an operation on the resource table . The database system according to claim 6, wherein:   The database system according to claim 7, wherein the client language environment is changed according to a language identification value included in the access request.   The database system according to claim 8, wherein the database system sets the client language environment as a language environment prioritizing the default setting, and provides a different client language environment for each client. An information processing method executed by an information processing apparatus that processes an access request from a client using a plurality of language environments,
The information processing apparatus is a resource table that stores multilingual resource data, and includes a resource table storage unit that stores a resource table that can be referred to from a column including multilingual data in a database. Prepared,
The information processing apparatus is
Identifying a language environment of the client accessing the information processing apparatus, and setting a language identification value for designating the client language environment in a language setting unit for setting the language environment;
Examining a command included in the access request and determining the presence of a command requesting an operation on the resource table ;
Receiving the command when it is determined that a command for requesting an operation for the resource table is included , and accessing the resource table by the language environment set in the language setting unit; ,
Registering a plurality of structured documents including values described in different languages for the same value as a child node in a record for each same value in the resource table . The language setting unit is secured in a memory area managed by the database, and the step of setting the language identification value includes:
Registering the language environment of the information processing apparatus in the memory area as a default setting;
The information processing method according to claim 11, further comprising: registering a language identification value included in an access request issued by the client as a client language environment at a different address in the memory area. The step of registering as a child node in the record for each same value is as follows:
The information processing method according to claim 11, further comprising: creating the child node with the client language environment prioritized over the default setting and registering the child node in the record.   The information processing method according to claim 13, further comprising a step of changing the client language environment according to a language identification value included in the access request. A computer-executable program for an information processing apparatus to execute an information processing method for processing an access request from a client using a plurality of language environments, the program including a resource storing multilingual resource data The information processing apparatus comprising a resource table storage unit that stores a resource table that is a table and can be referenced from a column including data expressed in a multilingual database .
Identifying a language environment of the client accessing the information processing apparatus, and setting a language identification value for designating the client language environment in a language setting unit for setting the language environment;
Examining a command included in the access request and determining the presence of a command requesting an operation on the resource table ;
Receiving the command when it is determined that there is a command for requesting an operation for the resource table, and accessing the resource table by the language environment set in the language setting unit;
Registering a plurality of structured documents including values written in different languages for the same value as a child node in a record for each of the same values in the resource table . program. The language setting unit is secured in a memory area managed by the database, and the step of setting the language identification value includes:
Registering the language environment of the information processing apparatus in the memory area as a default setting;
The program according to claim 15, comprising: registering a language identification value included in an access request issued by the client as a client language environment at a different address in the memory area. The step of registering as a child node in the record for each same value is as follows:
The program according to claim 16, further comprising the step of creating the child node as a language environment in which the client language environment is prioritized over the default setting and registering the child node in the record.   The program according to claim 17, further comprising changing the client language environment according to a language identification value included in the access request. An information processing apparatus that processes an access request from a client that uses a plurality of language environments, the information processing apparatus includes:
A resource table that stores multilingual resource data, and a resource table storage unit that stores a resource table that can be referred to from a column including multilingual data in the database;
A language setting unit for identifying a language environment of the client accessing the information processing apparatus and setting the language environment;
A client connection processing unit for setting a language identification value for designating a language environment of the client in the language setting unit;
A command processing unit that examines a command included in the access request and determines the presence of a command that requests an operation on the resource table ;
When the command processing unit determines that a command requesting an operation on the resource table is included, the command processing unit receives the command, and causes the resource table to be accessed by the language environment set in the language setting unit, A language resource processing unit that registers a plurality of structured documents including values described in different languages for the same value as a child node in a record for each same value in the resource table , and
The language setting unit includes a default setting unit that registers a language environment used as a default setting by the information processing apparatus, and the client connection processing unit includes a language identification value included in an access request issued by the client during the session. As a client language environment,
The client language environment is changed according to a language identification value included in the access request, and the client language environment is set as a language environment prioritizing the default setting, and a different client language environment is provided for each client. And
The language resource processing unit is configured to execute insertion, update, and deletion of the structured document using the language environment set by the language setting unit, a resource data insertion unit, a resource data update unit, An information processing apparatus including a resource / data deletion unit.

Images