JP2005216167A - System, method and program for database management and database registration request program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform version management of a database content properly and efficiently, realizing retention of consistency of the database in a relatively loose operation. <P>SOLUTION: An application server 100 includes a time information giving section 203 for giving date and time to the content for registration, and a transfer section 205 for transmitting the content for registration to a database server 110. The database server 110 includes a receiving section 301 for receiving the content for registration from the application server 100; a version update section 302 for updating the version of the content based on the date and time, when a content having the same search key as the received content for registration and having a new version is existent among the contents having been registered in the content database 120; and a registration section 303 for registering into the content database 120 the content for registration of which version is updated. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to database management for managing a database when registering or updating content information in a database when a plurality of registration processing servers for accepting content information and requesting registration in the database are distributed over a network. More particularly, the present invention relates to a database management system, a database management method, a database registration request program, and a database management program for maintaining database consistency.

  When multiple registration processing servers that accept content information and request registration to the database are distributed over the network, the registration of content from the registration processing server to the content database in one location on the network Or, when performing the update operation, the content of the same key in the database is updated from a plurality of registration processing servers, and data conflict may occur. For this reason, it is important to eliminate such data contention and maintain the consistency of the database.

  The following techniques are generally known as techniques for maintaining consistency when updating databases from such a plurality of registration processing servers.

  The first conventional technique creates a local data file that is a copy of the master data file when updating the master data file that is shared data that can be accessed simultaneously by many users, and tries to use the local data file as the master data file. Detected changes, check whether changes made to the local data file are in conflict with changes made by other users, and if there are conflicts, notify the user that there is a data conflict, An input from the user is received (see, for example, Patent Document 1). That is, in this prior art, the competition at the time of data change is monitored, and when there is a competition state, the user side resolves the competition.

  In the second prior art, when the same online document is shared among a plurality of servers on the network, a copy of the same document is distributed to each server, and a server that starts updating a certain document is transferred to another server. An update start notification is sent to the server, the update end notification is sent when the update is completed, and the server receiving the update start notification locks the update for the corresponding document and locks when the update end notification is received. It cancels (for example, refer patent document 2). In other words, in this prior art, while a document is being updated on a certain server, the document is locked. Therefore, the document cannot be updated from another server, and data conflict occurs when updating the same document. It has been resolved.

JP 11-161535 A Japanese Patent Laid-Open No. 11-272534

  In any of the above prior arts, it is possible to resolve a race condition when updating the same content. However, in an environment where registration processing servers distributed on the network can access the database at the same time, the user makes a content registration request. Since there is a possibility that the timing of each server making a registration request to the database may be shifted, there is a possibility that the registration processing to the database is not necessarily executed in the order in which the user makes a content registration request to the database. In this case, inconsistencies may occur in the version of the content registered in the database. Therefore, the database management system needs to have a function of resolving content data contention and appropriately managing content version.

  However, in the above-described conventional technology, there is a problem that the processing becomes complicated if processing for solving such data conflict and appropriately managing the version of content is provided. Further, the technique of Patent Document 2 has a problem that the original content data is locked, resulting in deadlock.

  By the way, when considering a database that stores component information such as an electronic catalog of electrical / electronic components and heavy electrical components as content, content registration and search systems are often operated on the following assumptions.

  First, the contents of a plurality of companies can be managed, browsed and registered on one Web site, and contents editing and correction authority is given in advance to a small number of contents managers of each company.

  Second, in the process of correcting the content, the period from when the original content is acquired to when it is corrected and the corrected content is registered again is very long. That is, editing online is rare and results in a long term transaction.

  Third, since there are few content managers in a company, it is rare that a plurality of users edit the same content at the same time. If the same content is edited at the same time, even if the update context is temporarily inconsistent, a large number of updates can be executed in a short time, and the correct version is finally given. This is not a big problem in operation.

  The present invention has been made in view of the above, and maintains consistency of a database in a relatively loose operation when registration processing servers that accept registration requests for content information in a database are distributed over the network. An object of the present invention is to provide a database management system, a database management method, a database registration request program, and a database management program capable of appropriately and efficiently performing version management of database content information.

In order to solve the above-described problems and achieve the object, the present invention provides a database server that manages a database in which content information including content and a version of the content is registered, and a client terminal device connected via a network. A database management system comprising: a plurality of registration processing servers that receive a registration request for content information and are connected to the database server via a network and request registration of the content information received by the database server in the database. Each of the plurality of registration processing servers receives content having the latest version from the content information registered in the database server from the database server, and has already been registered in the database using this content. Checkout means for generating information for editing the content information and transmitting the information to the client terminal device, and editing information indicating the editing content for the registered content information is received from the client terminal device, and received An editing unit that edits the registered content information based on editing information to generate content information to be registered, and a time for giving time information indicating the current time to the registration target content information edited by the editing unit Information providing means, transfer means for transmitting the content information to be registered, to which the time information is given by the time information giving means, to the database server, and the database server stores a database in which the content information is registered. Storage means and each of the plurality of registration processing servers. Receiving means for receiving the content information to be registered to which the time information is given, and among the content information already registered in the database, the content information to be registered and the search key received by the receiving means are When there is the registered content information that is the same and whose version is newer than the content information to be registered, the version of the content information to be registered and the version of the registered content information are based on the time information. A version updating unit that updates the version information, and a registration unit that registers, in the database, the registration target content information whose version has been updated by the version updating unit.

  Further, the present invention provides a hierarchical database in which content information including a hierarchical structure category item indicating a content category, an attribute corresponding to the category item, an attribute value corresponding to the attribute, and a version of the content is registered. Registration of the content information received from the database server to be managed and the client terminal device connected via the network, and the content information received from the database server connected to the database server via the network A plurality of registration processing servers that request the registration information, and each of the plurality of registration processing servers collectively requests registration of the content information to be registered to the classification item and the database server. Identification information of the registration processing server Processing server information storage means for storing the associated processing server information, and content having the latest version from the content information registered in the database server is received from the database server, and the content is used to store the content in the database. Checkout means for generating information for editing the already registered content information and transmitting it to the client terminal device; and editing information indicating edit contents for the registered content information is received from the client terminal device; An editing unit that edits the registered content information based on the received editing information to generate registration target content information, and the registration target content information edited by the editing unit is based on the processing server information. Content information to be registered Dispatch means for transmitting to the registration processing server corresponding to the classification item included, and transfer for transmitting the received content information to the database server when the content information to be registered is received from another registration processing server And a database storage means for storing a hierarchical database in which the content information is registered, a receiving means for receiving the content information to be registered from each of the registration processing servers, and the database Among the already registered content information, the registered content information received by the receiving means is the same as the classification item search key, and the registered version is newer than the registered content information. Whether there is content information In accordance with this determination result, the content information to be registered or the version of the registered content information is updated, and the content information to be registered whose version has been updated by the version update means. Registration means for registering in the database.

Further, the present invention provides a registration processing server for requesting registration of content information including a content and a version of the content, receiving the registration request for the content information from a client terminal device connected via a network, and the registration processing server To the database server that manages the database in which the content information is registered, and requests the database server to register the received content information in the database, and the database server receives the registration request and receives the content. A database management method for registering information in the database, wherein in each of the plurality of registration processing servers, content having the latest version is registered among the content information registered in the database server. A check-out step of generating information for editing content information already registered in the database using the content and transmitting the information to the client terminal device; and editing contents for the registered content information An editing step of receiving from the client terminal device, editing the registered content information based on the received editing information to generate content information to be registered, and the registration edited by the editing step A time information giving step for giving time information indicating the current time to the target content information, and a transfer step for sending the registration target content information to which the time information is given by the time information giving step to the database server; In the database server, The receiving step of receiving the registration target content information to which the time information is given from each of the plurality of registration processing servers, and the registration received by the receiving step among the content information already registered in the database When there is the registered content information whose search key is the same as the target content information and whose version is newer than the content information to be registered, the version of the content information to be registered and the registered content information A version updating step for updating the version information based on the time information, and a registration step for registering the registration target content information whose version has been updated by the version updating step in the database.

  In addition, the present invention provides a registration processing server that makes a registration request for content information including a hierarchically structured classification item indicating a content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content And receiving a request for registration of the content information from a client terminal device connected via a network, and accepting a request for a database server connected to the registration processing server via the network and managing a hierarchical database in which the content information is registered. A database management method for requesting registration of the content information in the database and receiving the registration request in the database server and registering the content information in the database, wherein each of the plurality of registration processing servers To the database server The content having the latest version from the recorded content information is received from the database server, and information for editing the content information already registered in the database is generated using the content, and the client terminal device A check-out step to be transmitted to the client, and edit information indicating edit contents for the registered content information is received from the client terminal device, and the registered content information is edited based on the received edit information. An editing step for generating the content information of the registration, and a registration process for collectively registering the registration target content information to the classification item and the database server for the registration target content information edited by the editing step Corresponds to server identification information A dispatch step for transmitting to the registration processing server corresponding to the classification item included in the content information to be registered based on the processing server information and the content information to be registered from another registration processing server A transfer step for transmitting the received content information to the database server; a reception step for receiving the content information to be registered from each of the registration processing servers in the database server; and a registration in the hierarchical database. Among registered content information, the registered content information that has the same search key for the classification item as the registration target content information received in the receiving step and has a newer version than the registered target content information Whether or not exists Then, based on the determination result, a version update step for updating the registration target content information or a version of the registered content information, and the registration target content information whose version has been updated by the version update step And a registration step of registering in the database.

  The present invention also accepts a registration request for content information including content and the version of the content from a client terminal device connected via a network, and manages a database connected via the network and registered with the content information. A database registration request program for requesting registration of the content information received in the database to the database server, and receiving content having the latest version from the content information registered in the database server from the database server. A checkout procedure for generating information for editing the content information already registered in the database using the content and transmitting the information to the client terminal device; and editing contents for the registered content information Editing procedure for receiving the editing information shown from the client terminal device, editing the registered content information based on the received editing information to generate content information to be registered, and the registration edited by the editing procedure A time information giving procedure for giving time information indicating the current time to the target content information, a transfer procedure for sending the registration target content information to which the time information has been given by the time information giving procedure to the database server, Is a database registration request program that causes a computer to execute.

  In addition, the present invention receives the request for registration of the content information from a registration processing server that requests registration of the content information in a database in which content information including the content and the version of the content is registered. A database management program for registering in a database, the receiving procedure for receiving the content information to be registered to which the time information is given from the registration processing server, and the content information already registered in the database, If the registered content information that has the same search key as the registration target content information received by the receiving procedure and has a newer version than the registration target content information exists, the version of the registration target content information And the registered content Database management for causing a computer to execute a version update procedure for updating a version of information based on the time information, and a registration procedure for registering the content information to be registered whose version has been updated by the version update procedure in the database It is a program.

  Also, the present invention provides a content including a hierarchical structure item indicating a content classification from a client terminal device connected via a network, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content A database registration request program that accepts a registration request for information, connects to a network, and requests a database server that manages a database that registers the content information to request registration of the content information in the database; The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. The client terminal A check-out procedure to be transmitted to a device and edit information indicating edit contents for the registered content information are received from the client terminal device, and the registered content information is edited and registered based on the received edit information. An editing procedure for generating target content information, and registration for registering the registration target content information edited by the editing procedure to the classification item and the database server in a batch Based on the processing server information associated with the processing server identification information, the dispatch procedure to be transmitted to the registration processing server corresponding to the classification item included in the registration target content information and the registration target content information are received. The received content information is stored in the database server. A transfer step of transmitting a database registration request program for executing the city on a computer.

In addition, the present invention provides a hierarchical database for registering content information including a hierarchical classification item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content. A database management program for registering the content information in the hierarchical database in response to a request for registration of the content information from a registration processing server that requests registration of content information, the content to be registered from the registration processing server Among the reception procedure for receiving information and the content information already registered in the hierarchical database, the content information to be registered received by the reception procedure is the same as the search key for the classification item, and The registered code whose version is newer than the content information to be registered. A determination is made as to whether or not the content information exists, a version update procedure for updating the content information to be registered or the version of the registered content information based on the determination result, and the version is updated by the version update procedure. A database management program for causing a computer to execute a registration procedure for registering the registered content information to be registered in the database.

  According to the present invention, when registration processing servers that accept registration requests for content information in the database are distributed on the network, the time information is finally converted to the time information even if a content information version conflict occurs temporarily. Therefore, in the relatively loose operation, version inconsistency does not become a serious problem. As a result, it is possible to maintain the consistency of the database and manage the version information of the database content information appropriately and appropriately. There is an effect that it can be performed efficiently.

  Further, according to the present invention, even when a plurality of registration processing servers are distributed on the network, the registration request timing is shifted by making a registration request to the database server 1410 for each classification item of the hierarchical database. Thus, the database content information version management can be performed appropriately and efficiently while maintaining the consistency of the database in a relatively loose operation.

  Exemplary embodiments of a database management system, a database management method, a database registration request program, and a database management program according to the present invention will be explained below in detail with reference to the accompanying drawings.

(Embodiment 1)
FIG. 1 is an explanatory diagram of a network configuration of the database management system according to the first embodiment of the present invention. As shown in FIG. 1, the database management system according to the present embodiment has a configuration in which a plurality of application servers 100 and a single database server 110 are connected via a network 150. Here, the network 150 is Ethernet (registered trademark) or the like, and the database server 110 and the plurality of application servers 100 construct a LAN (Local Area Network) environment. In this embodiment, the database server 110 and the plurality of application servers 100 construct a LAN environment. However, the present invention is not limited to this. For example, the database server 110 and the plurality of application servers 100 are connected to the Internet. The structure connected by may be sufficient.

  The database server 110 stores the content database 120 in its hard disk drive (HDD), and registers the content constituting the content database 120 in the content database 120 in response to a request from the application server 100 and Version management.

The application server 100 reads and edits content from the content database 120 in response to a request from the client terminal 130, and makes a request for registering the edited content in the content database 120 to the database server 110. The application server 100 constitutes a registration processing server in the present invention.

  A client terminal 130 is connected to the application server 100 via the Internet 140. The application server 100 provides various processing services to the content database of the database server 110 via the Web browser 131 installed in the client terminal 130.

  FIG. 2 is a block diagram illustrating a functional configuration of the application server 100. As shown in FIG. 2, the application server 100 mainly includes an editing unit 201, a registration receiving unit 202, a time information adding unit 203, a checkout unit 204, a transfer unit 205, and a receiving queue 206.

  In response to a request from the client terminal 130, the check-out unit 204 receives the latest version of the content of the search key designated by the client terminal 130 from the content database 120 of the database server 110, and uses this received content for the content database. Information for editing the content already registered in 120, for example, an html page for editing input to each item of the content, is generated and transmitted to the client terminal 130.

  The editing unit 201 receives from the client terminal 130 editing data for the registered content read by the checkout unit 204, for example, editing data such as editing input data to the above-described html page, and receives the received editing data. The process of editing the registered content is performed according to the process. The content that has been subjected to the editing process on the registered content in this way is called registration target content.

  The time information adding unit 203 performs processing for adding the current date and time (corresponding to the time information of the present invention) as the submission time to the edited content.

  The registration accepting unit 202 performs processing for storing the content added with the current date and time by the time information adding unit 203 in the accepting queue 206.

  The reception queue 206 is a first-in first-out queue (FIFO: First-In First-Out), in which contents with the current date and time are sequentially stored.

  The transfer unit 205 reads the content to which the current date and time is assigned from the top of the reception queue 206 and transmits the content to the database server 110 as the content to be registered.

  FIG. 3 is a block diagram showing a functional configuration of the database server 110. As shown in FIG. 3, the database server 110 includes a content database 120 in a receiving unit 301, a version updating unit 302, a registration unit 303, and an HDD. This HDD corresponds to the storage means in the present invention.

  The receiving unit 301 receives content to be registered in the content database 120 from the application server 100.

  The version updating unit 302 updates the version of the content to be registered received by the receiving unit 301 or the version of the content already registered in the content database 120. Specific version update processing will be described later.

  The registration unit 303 performs a process of registering the content to be registered whose version has been updated by the version update unit 302 in the content database 120.

  The content database 120 is a hierarchical database in which content is registered. In the present embodiment, as the content database 120, a database conforming to ISO13584 / Parts Library (PLIB), which is an international standard for electronic parts catalog exchange format, is used. This database conforming to the PLIB standardizes the data structure of component classification items and attributes provided by a component supplier so that any component data registered by any component supplier can be searched in the same manner.

  The content database 120 according to the present embodiment conforming to PLIB is composed of a dictionary and content. This content database 120 has a hierarchical structure in which a plurality of classification items are hierarchically related, and each classification other than the highest classification has a single parent classification, and each classification item is an attribute of the classification item of the classification item Each category item has a structure in which contents composed of attribute values corresponding to the attributes of the category item are registered.

  FIG. 4 is an explanatory diagram showing an example of the dictionary structure of the content database 120. As shown in FIG. 4, in the dictionary of the content database 120, a classification item “electronic product” is a root node, and nodes of classification items “personal computer” and “digital camera” are child nodes of the root node. It has an associated hierarchical structure. That is, “electronic product” is subdivided into two categories, “personal computer” and “digital camera”. In the content database 120 of the present embodiment, there are two hierarchies, but it may be configured to have a hierarchical structure of three or more hierarchies.

  Each classification item associated hierarchically has a unique attribute (indicated by a dotted line). Each category item inherits the attribute of the category item in the hierarchy above the category item in the hierarchical structure. For example, the attribute of the node “personal computer” includes an attribute (“model number”) defined in the “electronic product” of the root node, an attribute (“CPU”), and “standard memory capacity” defined in the node “personal computer”. , “Standard disk capacity”).

  Further, in the content database 120 of the present embodiment, a BSU code that guarantees that the code is unique worldwide is used as a code system for identifying each classification item and each attribute. In FIG. 4, the node “electronic product” is assigned “BAA code” “AAA001”, the node “personal computer” “AAA001”, the node “digital camera” “AAA002”, and the attribute “model number” “P1”. In this example, “P2” is assigned to “CUP”, “P3” is assigned to the attribute “standard memory capacity”, and “P4” is assigned to the attribute “standard disk capacity”.

As an example of the contents of the content database 120 having such a hierarchical structure, as shown in FIG. 7, classification hierarchies, attributes, and contents are stored. As shown in FIG. 7, the field names “Class BSU”, “version”, and “date / time” of the content database 120 are called system attributes and are attributes for the database server 110 to manage content, and are shown in FIG. It is different from the attributes defined in the dictionary. The value of “Class BSU” stores an identifier of a classification to which the corresponding content belongs, that is, a Class BSU code. In the example of FIG. 7, the value of the Class BSU code is “AAA001”, which indicates that all three contents shown in this example belong to the node “personal computer”.

  In FIG. 4, there are four attributes “P1”, “P2”, “P3”, and “P4” as the dictionary attributes defined as a dictionary in the ClassBSU code “AAA001”. It is assumed that values are stored only in the upper “P1” and “P2”. “P1” is a key for the user to uniquely identify products belonging to the classification “AAA001”. In the content database 120 of this example, there are two products with the search key “P1” having the value “E001” and different versions. The reason that different versions of content are registered even if the key values are the same is because it is assumed to be used for registration or correction of electronic catalog data.

  That is, if there is an error in the content initially registered by the content editor or registrant, the content is checked out from the content database 120 and read out, the read content is corrected, a new version is set, and the content database 120 is registered via the application server 100 and the database server 110. At this time, the model number of the product itself does not change if there is an error in the registered content as electronic part catalog data. Also, once the content data that has been made public is overwritten, for example, a searcher searching for content in the content database 120 searches the content and procures electronic components of the content before being overwritten. For example, inconvenience will occur later if it is used in another system. Therefore, in the content database 120 of the electronic component catalog according to the present embodiment, different versions of content are registered even if the search key value is the same.

  Accordingly, when updating the contents of the content database 120 as an electronic component catalog, the attribute value (“model number” in the examples of FIGS. 4 and 7) of the dictionary is the same and the system attribute “version” is set. The content is incremented by 1, that is, additionally registered as content having the latest version.

  Further, when the content database 120 is used as an electronic component catalog, two different pieces of information with the same model number are not released simultaneously. That is, it is assumed that the content version is not branched. Therefore, in the content database 120 of the present embodiment, the value of “version” is a natural number, and the version is incremented by 1 as the content is updated.

  The system attribute “date and time” is an attribute indicating the date and time when the application server 100 receives a content registration / modification request from the Web browser 131 of the client terminal 130.

  The content database 120 of the present embodiment is configured as a hierarchical database as described above, but is not limited to this, and a general relational database can also be used. In this case, since there is no classification item, the column of the system attribute “Class BSU” in FIG. 7 does not exist.

  Next, processing from content reception to registration in the content database 120 in the database management system according to the present embodiment configured as described above will be described.

First, the user specifies a desired key from the Web browser 131 of the client terminal 130 and requests the application server 100 to read content from the content database 120. The application server 100 requests the database server 110 to search for the corresponding content from the content database 120 using the search key specified by the checkout unit 204 at the client terminal 130. Upon receiving a search request from the application server 100, the database server 110 searches for content using a specified search key, and transmits the latest version of the searched content to the application server 100.

  When the application server 100 receives the retrieved content from the database server 110, the checkout unit 204 transmits the received content to the client terminal 130 and causes the web browser 131 to display the received content.

  The user edits the content displayed on the Web browser 131 at the client terminal 130, and transmits an edit request and a registration request to the application server 100. When the application server 100 receives the edit request and the registration request from the client terminal 130, the editing unit 201 edits the content acquired by the checkout unit 204 according to the editing data of the editing content performed at the client terminal 130. Do. Then, the editing unit 201 transmits a registration request to the database 120 for the edited content together with the edited content to the registration receiving unit 202. The registration receiving unit 202 receives the registration request from the editing unit 201 and the edited content as registration target content.

  When the application server 100 transmits the latest version of the content to the client terminal 130, several methods can be considered. For example, the entire content of the latest version including “version information” may be transmitted, or a part of the content excluding “version information” by generating an ID associated with the latest version of content on the application server An html page may be formed from the ID pair and transmitted.

  In the latter case, when receiving an edit request and a registration request from the client terminal 130, the application server 100 generates content corresponding to the edit data by the client terminal 130 from the original registered content obtained from the associated ID. Then, the data is transferred to the editing unit 201, and the editing unit 201 performs editing processing according to the editing data.

  FIG. 5 is a flowchart showing a procedure of processing for making a registration request to the database server 110 of the content to be registered edited by the editing unit 201.

  When the registration receiving unit 202 receives the content to be registered, the time information adding unit 203 gives the current date and time at the time of reception to the content to be registered (step S501). Next, the registration receiving unit 202 registers the content to be registered with the current date and time in the reception queue 206 (step S502). The process of assigning the current date and time and registering in the reception queue 206 in step S501 is performed for all the contents received by the registration receiving unit 202 (step S503).

  When all the registration target contents are registered in the acceptance queue, the transfer unit 205 acquires the registration target contents from the top of the reception queue 206 (step S504), and transmits the acquired registration target contents to the database server 110. (Step S505). The acquisition processing of the registration target content from the acceptance queue and the transmission processing of the registration target content to the database server 110 in steps S504 and S505 are performed for all the registration target content stored in the reception queue 206. (Step S506). By such processing, a content registration request is made to the database server 110, and all the application servers 100 on the network 150 make this registration request.

  In the database server 110, the reception unit 301 receives the registration target content from the application server 100, and passes the received registration target content to the version update unit 302.

  FIG. 6 is a flowchart showing a procedure of version update processing by the version update unit 302 of the database server 110. In the database server 110 according to the present embodiment, the version assigned to the registration target content for which the registration request is made later in time from the client terminal 130 to the application server 100 is first sent in time. The version of the content is updated according to a version policy that updates the version to be newer than the version assigned to the registered content.

  When the version update unit 302 receives the registration target content from the reception unit 301, the version update unit 302 acquires the received version of the registration target content from the version field in the content (step S601).

  Then, a content that has the same key value as the content to be registered and has a version (newer) than the content to be registered is searched from the content database 120 to check whether such content exists (step S602). If it is determined that there is no content database 120 that has the same search key value as the registration target content and a version higher than the registration target content (step S602: No), The version is incremented by 1 (step S606) and passed to the registration unit 303 (step S605). Then, the registration unit 303 registers the content whose version has been updated in the content database 120.

  On the other hand, if it is determined in step S602 that content that has the same search key value as the registration target content and a version higher than the registration target content exists in the content database 120 (step S602: Yes), the registration target The already registered contents having the same key as that of the contents to be registered and the contents to be registered are sorted in ascending order of time (step S603). Then, the content version is reassigned so that the value increases from the earliest time of the sorted content (step S604). Then, the content to be registered whose version has been reassigned is passed to the registration unit 303 (step S605), and the registration unit 303 registers the content to be registered whose version has been updated in the content database 120.

  Through the processing as described above, content version update processing and content registration processing to the content database 120 are performed. As a result, the content database stores the registration request from the client terminal 130 to the application server 100 and the version of the content that has been received by the application server 100 before the registration request from the client terminal 130 and the acceptance by the application server 100. It is updated and registered with a value larger than the version of the content made.

  Next, a specific example from the content registration request to the content database 120 by the application server 100 and the database server 110 will be described.

FIG. 7 illustrates the process of reading the content from the content database 120, editing it, and registering it in the content database 120.
It is explanatory drawing which shows the state in which the content is edited by b browser 131. FIG.

  The users of the client terminals 130a and 130b make a search request to the content database 120 under the search condition “attribute“ P1 ”=“ E001 ””, and read from the content database 120 via the database server 110 and the application server 100a.

  At this time, for the content having the same key (attribute P1 in this example), the content having the latest system attribute “version” is read. Next, the user of the client terminal 130a modifies the value of P2 (limited to attributes other than the key) from “T” to “T ′” as shown in FIG. 7, and changes the date to “8/8 9:00”. A registration request is transmitted to the application server 100a, and content to be registered is submitted. At this time, in the application server 100a, a registration request is transmitted from the editing unit 201 to the registration receiving unit 202 at the same time.

  On the other hand, the user of the client terminal 130b modifies the value of P2 (limited to attributes other than the key) from “T” to “T” as shown in FIG. 7, and changes the date to “8/8 9:01”. A registration request is transmitted to the application server 100b. At this time, in the application server 100b, a registration request is transmitted from the editing unit 201 to the registration receiving unit 202 at the same time.

  FIG. 8 is an explanatory diagram showing a flow of processing in which the registration target content received by the application servers 100 a and 100 b is transmitted to the database server 110 and registered in the content database 120.

  In the application servers 100a and 100b, the registration receiving unit 202 receives the registration request from the editing unit 201 and the content to be registered, and the time information adding unit 203 gives the date and time of reception to the content to be registered. As shown in FIG. 8, the application server 100a is given the date “8/8 9:00” at the time of acceptance, and the application server 100b is given the date “8/8 9:01” at the time of acceptance. Will be. Then, the registration receiving unit 202 of each of the application servers 100 a and 100 b registers the content to be registered with the date and time added to the reception queue 206. FIG. 8 shows a state in which the content to be registered is registered in the acceptance queue.

  In this embodiment, after the date is given to the registration target content, the registration target content to which the date is given is registered in the reception queue 206. However, the registration target content is first registered in the reception queue 206. The registration date and time may be assigned to the registration target content registered in the acceptance queue after registration.

  Next, the transfer unit 205 of the application servers 100a and 100b reads the content to be registered from the top of the acceptance queue 206 at an arbitrary timing and transmits it to the database server 110, and sends it to the content database 120 to the database server 110. A registration request is made. At this time, since the transfer unit 205 makes a registration request to the database server 110 at an arbitrary timing in each of the application servers 100a and 100b, the registration requests are not necessarily made in the same order as the order of time of acceptance between the servers. As a result, inconsistency may occur in that the registration order in the content database 120 is not in time order.

Here, the date and time at which the content to be registered is received is earlier in time for the content 801 received by the application server 100a than the content 802 received by the application server 100b. Consider a case where a registration request is made at 110. Hereinafter, description will be given according to the processing of the version update unit 302 of FIG. 6 described above.

  In the database server 110, when the receiving unit 301 receives the registration target content 802, the version update unit 302 acquires the version of the registration target content 802 (step S601). In the example of FIG. 8, version = 2. Then, it is checked whether or not there is content having the same key value and a version greater than 2 in the content database 120 (step S602). In the example of FIG. 8, since there is no such content (step S602: No), the version of the registered content is incremented by 1 to 3 (step S606). Then, the registration target content 802 is transferred to the registration unit 303, and the registration unit 303 registers the transferred content in the content database 120. The content database 120 in FIG. 8 shows a state in which the content 802 is registered.

  It is assumed that after the registration target content 802 is registered in the content database 120, the registration target content 801 that is temporally ahead of the content 802 is transmitted from the application server 100a to the database server 110. FIG. 9 is an explanatory diagram showing the flow of processing for registering the registration target content 801 in the content database 120.

  In the database server 110, when the receiving unit 301 receives the registration target content 801, the version update unit 302 acquires the version of the registration target content 801 (step S601). In the example of FIG. 9, version = 2. Then, it is checked whether or not there is content having the same key value and a version greater than 2 in the content database 120 (step S602). In the example of FIG. 9, there is content 802 (version = 3) already registered in the content database 120 by a registration request from the application server 100b. For this reason, the contents 801 to be registered and the registered contents 802 are sorted in order of time (step S603), and the version is reassigned so that the value increases from the earliest time (step S604). As a result, the content 801 to be registered is updated to version 3, and the already registered content is updated to version 4. That is, the content version is set in the order of the editing request from the client to the application servers 100a and 100b and the reception time of the application servers 100a and 100b regardless of the time of the registration request to the database server 110. Then, the registration target content 801 is transferred to the registration unit 303, and the registration unit 303 registers the transferred content 801 in the content database 120. FIG. 10 is an explanatory diagram showing the content database 120 in a state where the contents 801 and 802 whose versions are updated are registered.

As described above, in the database management system according to the present embodiment, each of the plurality of application servers 100 indicates the time indicating the date and time on the content to be registered, which is the content already registered in the content database 120 in response to a request from the client terminal 130. The registration target content to which the information is added and the time information is sent to the database server 110, and the database server 110 receives the registration target content to which the date and time are given from each of the application servers 100, and the database If there is registered content information whose search key is the same as the received content information and the version is newer than the registered content information, the registered target information Conte The version of the content and the version of the registered content information are updated so as to increase in order of date and time and are registered in the content database 120. Therefore, when the application server 100 is distributed on the network, Even if a content version conflict occurs, it is updated to the correct version based on the date and time. Therefore, in a relatively loose operation, the version conflict does not matter so much. The content version management of the content database 120 can be performed appropriately and efficiently while realizing the retention.

(Embodiment 2)
In the database management system according to the first embodiment, the version assigned to the content to be registered for which the edit request is made to the application server 100 later in time is the version of the registration target for which the edit request has been made earlier in time. In the database management system according to the second embodiment, only the content to be registered for which an edit request has been made earlier is stored in the content database 120. The content to be registered is not registered when an edit request is made to the application server 100 later in time.

  The configuration of the database management system according to the second embodiment, and the configurations of the application server 100, the database server 110, and the content database 120 are the same as those in the first embodiment, and thus description thereof is omitted.

  Further, the content registration request processing for the database server 110 by the application server 100 according to the second embodiment is the same as that of the first embodiment, and thus the description thereof is omitted.

  Next, content registration processing and version update processing by the database server 110 according to the present embodiment will be described. FIG. 11 is a flowchart illustrating a procedure of version update processing by the version update unit 302 of the database server 110. The database server 110 according to the present embodiment updates the version of the content according to a version policy for registering only the registration target content for which an edit request has been made to the application server 100 earlier in time.

  Similar to the database server 110 of the first embodiment, the reception unit 301 receives content to be registered from the application server 100. When the version update unit 302 receives the registration target content from the reception unit 301, the version update unit 302 acquires the received version of the registration target content from the version field in the content (step S1101).

  Then, a content that has the same key value as the content to be registered and has a version (newer) than the content to be registered is searched from the content database 120 to check whether such content exists (step S1102). If it is determined that there is no content in the content database 120 that has the same key value as the content to be registered and a version greater than the content to be registered (step S1102: No), the version of the content to be registered is changed. It is incremented by 1 (step S1107) and passed to the registration unit 303 (step S1106). Then, the registration unit 303 registers the content whose version has been updated in the content database 120.

  On the other hand, if it is determined in step S1102 that there is content in the content database 120 that has the same key value as the content to be registered and a version higher than the content to be registered (step S1102: Yes), the content to be registered Among the already registered contents having the same key as the contents to be registered, the contents with the latest date and time are deleted with reference to the date and time field (step S1103).

  Next, it is determined whether or not the content deleted in step S1103 is the content to be registered received from the application server 100 (step S1104). If it is determined that the content to be registered has not been deleted, that is, if the date and time of the already registered content is the latest and it is determined that this registered content has been deleted (step S1104: No) ), The version of the content to be registered received from the application server 100 is incremented by 1 (step S1105). Then, the registration target content with the version incremented is passed to the registration unit 303 (step S1106), and the registration unit 303 registers the registration target content with the updated version in the content database 120.

  On the other hand, if it is determined in step S1104 that the content to be registered has been deleted, that is, if the date and time of the content to be registered is the latest and it is determined that the content to be registered has been deleted (step S1104: Yes), the process ends without passing the content to be registered to the registration unit 303. Through the processing as described above, content version update processing and content registration processing to the content database 120 are performed. As a result, the content database is registered with the edit request to the application server 100 and the content that has been received by the application server 100 first.

  Next, a specific example from the content registration request to the content database 120 by the application server 100 and the database server 110 will be described.

  FIG. 12 is an explanatory diagram showing a flow of processing in which the registration target content received by the application servers 100 a and 100 b is transmitted to the database server 110 and registered in the content database 120.

  Similar to the first embodiment, the application server 100a assigns the date and time “8/8 9:00” at the time of acceptance to the content to be registered, stores the content 1201 to be registered in the acceptance queue, and At 100 b, the date and time “8/8 9:01” at the time of acceptance is assigned to the content to be registered and stored in the acceptance queue 126.

  Next, the transfer unit 205 transmits the content to be registered to the database server 110. Also in the present embodiment, as in the first embodiment, the date and time when the content to be registered is received is earlier in time for the content 1201 received by the application server 100a than the content 1202 received by the application server 100b. However, a case where a registration request is made to the database server 110 first from the application server 100b is considered. Hereinafter, description will be given according to the processing of the version update unit 302 of FIG. 11 described above.

In the database server 110, when the receiving unit 301 receives the registration target content 1202, the version update unit 302 acquires the version of the registration target content 1202 (step S1101). In the example of FIG. 12, version = 2. Then, it is checked whether or not there is content having the same key value and a version greater than 2 in the content database 120 (step S1102). In the example of FIG. 12, since there is no such content (step S1102: No), the version of the registered content is incremented by 1 to 3 (step S1107). Then, the content 1202 to be registered is transferred to the registration unit 303, and the registration unit 303 registers the transferred content in the content database 120. The content database 120 in FIG.
Reference numeral 202 denotes a registered state.

  Assume that after the registration target content 1202 is registered in the content database 120, the registration target content 1201 that is temporally ahead of the content 802 is transmitted from the application server 100 a to the database server 110.

  In the database server 110, when the content 1201 to be registered is received by the receiving unit 301, the version of the content 1201 to be registered is acquired by the version update unit 302 (step S1101). In the example of FIG. 12, version = 2. Then, it is checked whether or not there is content having the same key value and a version greater than 2 in the content database 120 (step S1102). In the example of FIG. 12, there is content 1202 (version = 3) already registered in the content database 120 by a registration request from the application server 100b. Therefore, the registered content 1202 with the new date / time is deleted from the content 1201 to be registered and the registered content 1202 (step S1103). In this example, the content 1201 to be registered is not deleted (step S1104: No), so the version of the content 1201 to be registered is incremented by 1 to set version = 3, and the content 1201 to be registered is registered in the registration unit. 303 (step S1106). The registration unit 303 registers the delivered content in the content database 120. The content database 120 in FIG. 13 shows a state in which the content 1201 is registered.

  As described above, in the database management system according to the present embodiment, each of the plurality of application servers 100 indicates the date and time for the content to be registered, which is the content already registered in the content database 120 in response to a request from the client terminal 130. The time information is added, and the registration target content with the time information is transmitted to the database server 110. The database server 110 receives the registration target content with the date and time from each of the application servers 100, and If there is registered content information that has the same search key as the received content information and has a newer version than the content information to be registered, among the content already registered in the database of The content information with the oldest date and time is updated to the latest version of the content version and the registered content information version, so there is no problem with version conflicts in relatively loose operations, and the content database The content version management of the content database 120 can be appropriately and efficiently performed while maintaining 120 consistency.

(Embodiment 3)
In the database management systems of the first and second embodiments, a general database such as a hierarchical database or a relational database is used as a content database, and version management is performed at the date and time when the registration request is received. In the database management system 3, a hierarchical database is used as a content database, and version management is performed without using date and time information.

  The database management system of this embodiment has a plurality of application servers 1400 and a database server 1410, and has the same network as that of the first embodiment.

  The database server 1410 stores the content database 1420 in its hard disk drive (HDD), and registers the content constituting the content database 1420 in the content database 1420 in response to a request from the application server 1400 and Version management.

  The application server 1400 reads content from the content database 1420 in response to a request from the client terminal 130, edits the read content, and requests the database server 1410 to register the edited content in the content database 1420. It is. This application server 1400 constitutes a registration processing server in the present invention.

  A client terminal 130 is connected to the application server 1400 via the Internet. The application server 1400 is configured to provide various processing services to the content database of the database server 1410 via the Web browser 131 installed in the client terminal 130.

  FIG. 14 is a block diagram showing a functional configuration of the application server 1400. As illustrated in FIG. 14, the application server 1400 mainly includes an editing unit 201, a registration receiving unit 1403, a dispatch unit 1402, a checkout unit 204, a transfer unit 205, a receiving queue 206, and a processing server table 1401.

  Since the checkout unit 204, the editing unit 201, and the transfer unit 205 have the same functions as those of the application server 1400 according to the first embodiment, description thereof is omitted.

  The processing server table 1401 is a data file that defines, for each classification item (Class BSU), a server name of the application server 1400 that collectively performs a registration request to the database server 1410 for contents to be registered. The processing server table 1401 associates the attribute of the classification item of the content database 1420 with the server name of the application server 1400 that collectively performs the registration request for the content to be registered to the database server 1410. . FIG. 16 is an explanatory diagram showing an example of the processing server table 1401. As shown in FIG. 16, in this embodiment, the server name is associated with the classification item, but other information such as an IP address that can identify the application server 1400 can be used.

  The dispatch unit 1402 registers the registration target content obtained by editing the content already registered in the content database 1420 with reference to the processing server table in the application server 1400 for the classification item corresponding to the Class BSU code of the registration target content. The content is transmitted.

  The registration accepting unit 1403 performs processing for storing, in the accepting queue 206, the content to be registered for the classification item specified by the processing server table 1401 so that the server itself makes a registration request. The content to be registered may be received from the client terminal 130 by another application server 1400 and received from the other application server, or may be received from the client terminal 130 within the own server.

  FIG. 15 is a block diagram showing a functional configuration of the database server 1410. As shown in FIG. 15, the database server 1410 includes a reception unit 301, a version update unit 1412, a registration unit 303, and a content database 1420 in the HDD.

  The receiving unit 301 receives content to be registered in the content database 120 from the application server 100.

The version update unit 1412 updates the version of the content to be registered received by the reception unit 301 or the version of the content already registered in the content database 1420. Specific version update processing will be described later.

  The registration receiving unit 202 performs processing for registering the content to be registered whose version has been updated by the version update unit 302 in the content database 1420.

  As the content database 1420 in the present embodiment, only a hierarchical database can be used, and a relational database cannot be used. The data structure of the content database 1420 is a hierarchical database related to the electronic component catalog.

  Next, processing from content reception to registration in the content database 1420 in the database management system according to the present embodiment configured as described above will be described.

  The user requests the application server 1400 to read the content of a desired classification item from the content database 1420 from the Web browser 131 of the client terminal 130. The application server 1400 requests the database server 1410 to search the content of the classification item specified by the client terminal 130 by the checkout unit 204. In response to the search request from the application server 1400, the database server 1410 searches the content of the designated classification item, and transmits the searched content to the application server 1400.

  Upon receiving the content retrieved from the database server 1410, the application server 1400 causes the checkout unit 204 to transmit the received content to the client terminal 130 for display on the web browser 131.

  The user edits the content displayed on the Web browser 131 on the client terminal 130, and transmits an edit request and a registration request to the application server 1400. In the application server 1400, when the editing request and the registration request are received from the client terminal 130, the editing unit 201 performs the editing content performed on the client terminal 130 on the content acquired by the checkout unit 204. Then, the editing unit 201 transmits a registration request to the database 1420 of the edited content together with the edited content to the registration receiving unit 1403. The registration receiving unit 1403 receives the registration request from the editing unit 201 and the edited content as registration target content.

  FIG. 17 is a flowchart illustrating a processing procedure for requesting registration to the database server 110 of the content to be registered edited by the editing unit 201.

  When the registration receiving unit 1403 receives the content to be registered, the dispatch unit 1402 refers to the processing server table 1401 and acquires the name of the application server 1400 corresponding to the classification item of the content to be registered (step S1701). Then, the dispatch unit 1402 determines whether or not the application server 1400 having the acquired name is its own server (step S1702). If it is determined in step S1702 that the server is the server itself (step S1702: Yes), the registration receiving unit 1403 registers the content to be registered in the receiving queue 206 (step S1704).

On the other hand, if it is determined in step S1702 that the application server 1400 having the name acquired from the processing server table 1401 in step S1701 is not its own server, the content to be registered is transmitted to the application server 1400 having the acquired name. Then, the dispatch unit 1402 checks whether or not the registration target content received by the registration reception unit 1403 still exists (step S1705). For all the registration target content received, the above steps S1701 to S1704 are performed. Repeat the process.

  FIG. 18 is a flowchart showing a registration request procedure to the database server 1410 for contents to be registered by the application server 1400. The application server 1400 that performs this processing is the application server 1400 that is designated for each classification item as a server that collectively performs registration request processing in the processing server table 1401.

  In the application server 1400, the registration target content is received from the other application server 1400 by the registration receiving unit 1403, and the received registration target content is stored in the reception queue 206.

  If the server itself is a server that collectively processes the registration request processing for the registration target content received from the client terminal 130, the registration reception unit 1403 receives the registration target content in step S1704 in FIG. Registered in the queue 206.

  Therefore, first, the transfer unit 205 acquires the registration target content from the top of the acceptance queue 206 (step S1801), and transmits the acquired registration target content to the database server 1410 (step S1802). The acquisition processing of the registration target content from the acceptance queue and the transmission processing of the registration target content to the database server 1410 in steps S1801 and S1802 are performed for all the registration target content stored in the reception queue 206. (Step S1803). By such processing, a content registration request to the database server 1410 is made.

  Next, registration processing of content to be registered in the content database 1420 by the database server 1410 will be described. In the database server 110, the reception unit 301 receives registration target content from the application server 1400, and passes the received registration target content to the version update unit 1412.

  FIG. 19 is a flowchart showing the procedure of version update processing by the version update unit 1412 of the database server 1410. The database server 1410 of this embodiment gives priority to the version of the content to be registered that has arrived at the database server 1410 first in time, and updates the version so that the version of the content to be registered that arrives later is new. ing.

  When the version update unit 302 receives the content to be registered from the receiving unit 301, the version update unit 302 acquires the received version of the content to be registered from the version field in the content (step S1901).

Then, a content having the same search key as the content to be registered and having a version (newer) having a higher version than the content to be registered is searched from the content database 120 to check whether such content exists (step) S1902). If it is determined that content having the same search key value as the content to be registered and a version having a large version does not exist in the content database 120 (step S1902: No), the version of the content to be registered is only 1. Increment (step S1904) and pass to the registration unit 303 (step S1905). Then, the registration unit 303 registers the content whose version has been updated in the content database 120.

  On the other hand, if it is determined in step S1902 that there is content in the content database 120 that has the same search key value as the content to be registered and has a version higher than the content to be registered (step S1902: Yes), The version of the content to be registered is updated by one more than the maximum version of the already registered content (step S1903). The updated registration target content is passed to the registration unit 303 (step S1904), and the registration unit 303 registers the registration target content whose version has been updated in the content database 1420. Through the processing as described above, content version update processing and content registration processing to the content database 1420 are performed. As a result, the content requested after the editing request to the application server 1400 and the acceptance by the application server 1400 is updated and registered in the content database with a value larger than the version of the content that was previously requested and accepted. Will be.

  Next, a specific example from the content registration request to the content database 1420 by the application server 1400 and the database server 1410 will be described. Hereinafter, description will be made in association with each step of FIGS.

  FIG. 20 is an explanatory diagram showing a state from when content is read from the content database 1420 until it is stored in the acceptance queue 206 of the application server 1400a. In the example of FIG. 20, the processing server table 1401 determines that the application server A1400a is a server that collectively requests the database server 1410 for the content of the ClassBSU code “AAA001” in the content database 1420. (See FIG. 16).

  The users of the client terminals 130a and 130b make a search request from the content database 1420 under the search condition “attribute“ P1 ”=“ E001 ””, and read from the content database 1420 via the database server 1410 and the application servers 1400a and 1400b.

  At this time, for the content having the same key (attribute P1 in this example), the content having the latest system attribute “version” is read. Next, the user of the client terminal 130a corrects the value of P2 (limited to attributes other than the key) from “T” to “T ′”, and the application server A 1400a at the time of “8/8 9:00” on the date and time. The registration request is transmitted to the content 2000a to be registered. At this time, in the application server A 1400a, a registration request is transmitted from the editing unit 201 to the registration receiving unit 1403 at the same time.

  On the other hand, the user of the client terminal 130b modifies the value of P2 (limited to attributes other than the key) from “T” to “T”, and registers it in the application server B 100b at the date “8/8 9:01”. The request is transmitted and the content 2000b to be registered is submitted. At this time, in the application server B 1400b, a registration request is transmitted from the editing unit 201 to the registration receiving unit 202 at the same time.

Each of the application server A 1400a and the application server B 1400b refers to the processing server table 1401, and determines a server that collectively performs a registration request for content whose ClassBSU is “AAA001” (step S1701). In this example, since it is the application server A 1400a, the application server A registers the content 2000a to be registered in the acceptance queue 206 (step S170).
4).

  On the other hand, the application server B 1400b transmits the content 2000b to be registered to the application server 1400a (step S1703). The application server A 1400a receives the registration target content 2000b from the application server 1400b and registers the received registration target content 2000b in the acceptance queue 206.

  Here, in the application server A 1400a, it is assumed that the registration target content 2000a and the registration target content 2000b are registered in the acceptance queue 206 in this order. The acceptance queue 206 in FIG. 20 shows such a state.

  FIG. 21 is an explanatory diagram showing the flow of processing in which the content 2000a to be registered is transmitted to the database server 110 and registered in the content database 1420.

  In the application server 1400a, the transfer unit 205 reads the content to be registered from the head of the acceptance queue 206 at an arbitrary timing and transmits it to the database server 110. A request for registration to the content database 1420 is sent to the database server 1410. Done.

  In the example of FIG. 21, since the content 2000a to be registered is registered in the acceptance queue 206 first, it is acquired from the content 2000a to be registered (step S1801) and transmitted to the database server 1410 to make a registration request. (Step S1802).

  In the database server 1410, when the receiving unit 301 receives the registration target content 802, the version update unit 1412 acquires the version of the registration target content 2000a (step S1901). In the example of FIG. 21, version = 2. Then, the content database 1420 checks whether there is a content having the same search key value as the registration target content 2000a and having a version greater than 2 (step S1902). In the example of FIG. 21, since there is no such content (step S1902: No), the version of the content 2000a to be registered is incremented by 1 to 3 (step S1904). Then, the registration target content 2000a is transferred to the registration unit 303, and the registration unit 303 registers the transferred content in the content database 1420. The content database 1420 in FIG. 21 shows a state in which the content 2000a is registered.

  FIG. 22 is an explanatory diagram showing the flow of processing for registering the content 2000b to be registered in the content database 1420.

  In the application server 1400a, the transfer unit 205 acquires the content 2000b to be registered that is still stored in the acceptance queue 206 (step S1801), and transmits it to the database server 1410 (step S1802).

In the database server 1410, when the receiving unit 301 receives the registration target content 2000b, the version update unit 302 acquires the version of the registration target content 2000b (step S1901). In the example of FIG. 21, version = 2. Then, the content database 1420 checks whether there is a content having the same search key value as the content to be registered 2000b and having a version greater than 2 (step S1902). In the example of FIG. 22, there is content 2000a (version = 3) already registered in the content database 1420 by the registration request from the application server 1400a, and the maximum version of this content key is 3, which is the version of the content 2000a. . Therefore, the version of the content 2000b to be registered is updated to 4 that is 1 larger than the maximum version 3 (step S1903). Then, the registration target content 2000b is transferred to the registration unit 303, and the registration unit 303 registers the transferred content 2000b in the content database 1420. The content database 1420 shown in FIG. 22 shows a state in which the contents 2000a and 2000b whose versions are updated are registered.

  As described above, in the database management system according to the present embodiment, content information including a hierarchical classification item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and the version of the content is stored. When managing the registered hierarchical database, each of the plurality of application servers 1400 sets the contents to be registered, which are contents already registered in the database in response to a request from the client terminal 130, as classification items and the database server 1410. Application corresponding to the classification item included in the content information to be registered based on the processing server table 1401 in which the server names of the application servers 1400 that collectively perform registration requests for the content information to be registered are associated with each other server When the content to be registered is received from another application server 1400, the received content is transmitted to the database server 1410 at a time. The database server 1410 receives the content to be registered from the application server 1400. Whether or not there is registered content that is already registered in the database and has the same search key as the classification item received and whose version is newer than the registered content. If such content exists, the version of the content to be registered is updated by incrementing by 1 from the latest version of the registered content, so that the application server 1400 is on the network. When distributed In FIG. 4, the registration request to the database server 1410 for each classification item at once does not cause a deviation in the timing of the registration request, and the database content information is maintained while maintaining the consistency of the database in a relatively loose operation. There is an effect that the version management of can be performed appropriately and efficiently.

(Embodiment 4)
In the database management system according to the third embodiment, priority is given to the content to be registered that has arrived at the database server 1410 first in time, and the version is updated so that the version of the content that has arrived later is updated. However, in the database management system according to the fourth embodiment, when the registration target content that has arrived first is registered in the content database 1420, the subsequent correction is not permitted and the registration in the content database 1420 is not performed. It is.

  The configuration of the database management system according to the fourth embodiment, and the configurations of the application server 1400, the database server 1410, and the content database 1420 are the same as those in the third embodiment, and thus the description thereof is omitted.

  Further, the processing for requesting content registration to the database server 1410 by the application server 1400 according to the fourth embodiment is the same as that according to the third embodiment, and a description thereof will be omitted.

Next, content registration processing and version update processing by the database server 1410 according to the present embodiment will be described. FIG. 23 is a flowchart showing the procedure of version update processing by the version update unit 1412 of the database server 1410. The database server 1410 according to the present embodiment updates the version of the content according to a version policy for registering only the content to be registered, which is first requested in the application server 1400 in terms of time.

  First, the database server 1410 receives content to be registered from the application server 1400 by the receiving unit 301 as in the third embodiment. Upon receiving the registration target content from the receiving unit 301, the version update unit 1412 acquires the received version of the registration target content from the version field in the content (step S2301).

  Then, the content database 1420 is searched for content having a version (newer) than the content to be registered, and it is checked whether or not such content exists (step S2302). If it is determined that there is no content in the content database 120 that is greater in version than the content to be registered (step S2302: No), the version of the content to be registered is incremented by 1 (step S2304), and the registration unit It is passed to 303 (step S2305). Then, the registration unit 303 registers the content whose version is updated in the content database 1420.

  On the other hand, if it is determined in step S2302 that content whose version is higher than the content to be registered exists in the content database 1420 (step S2302: Yes), the content to be registered is deleted (step S2303). As a result, the content to be registered is not registered in the content database 1420, and only the content to be registered for which an edit request has been made to the application server 1400 in time is registered.

  Next, a specific example from the content registration request to the content database 1420 by the application server 1400 and the database server 1410 will be described.

  FIG. 24 is an explanatory diagram showing a flow of processing in which the registration target content received by the application servers 1400a and 1400b is transmitted to the database server 110 and registered in the content database 120. Here, the processing and state from reading the content from the content database 1420 to storing it in the acceptance queue 206 of the application server 1400a are the same as those in the third embodiment described with reference to FIG.

  That is, as in the third embodiment, the registration target content 2000a received by the own server and the registration target content 2000b received from the application server 1400b are sequentially registered in the reception queue of the application server 1400a, and the registration target content 2000a. It is assumed that the registration request to the database server 1410 is made first and is registered in the content database 1420 as version 3 first. The content database 1420 in FIG. 24 shows such a state.

  Next, the transfer unit 205 transmits the content 2000b to be registered to the database server 1410.

In the database server 1410, when the receiving unit 301 receives the registration target content 2000b, the version update unit 1412 acquires the version of the registration target content 2000b (step S2301). In the example of FIG. 24, version = 2. Then, it is checked whether or not content having a version greater than 2 exists in the content database 120 (step S2302). In the example of FIG. 24, content 2000a (version = 3) already registered in the content database 1420 exists. For this reason, the content 2000b to be registered is deleted (step S2303), and registration in the content database 1420 is not performed. FIG. 25 is an explanatory diagram showing the contents of the final content database 1420. As shown in FIG. 25, in the content database 1420, only the content 2000a for which the registration request was previously made to the database server 1410 is registered as version 3, and the content 2000b for which the registration request was made later is not registered.

  As described above, in the database management system according to the present embodiment, content information including a hierarchical classification item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and the version of the content is stored. When managing the registered hierarchical database, each of the plurality of application servers 1400 sets the contents to be registered, which are contents already registered in the database in response to a request from the client terminal 130, as classification items and the database server 1410. Application corresponding to the classification item included in the content information to be registered based on the processing server table 1401 in which the server names of the application servers 1400 that collectively perform registration requests for the content information to be registered are associated with each other server When the content to be registered is received from another application server 1400, the received content is transmitted to the database server 1410 at a time. The database server 1410 receives the content to be registered from the application server 1400. Whether or not there is registered content that is already registered in the database and has the same search key as the classification item received and whose version is newer than the registered content. If such content exists, the content information to be registered is deleted, and the content requested to be registered later is not registered. Therefore, the application server 1400 is distributed on the network. In case By making a registration request to the database server 1410 for each classification item at once, there is no deviation in the timing of the registration request, and the database content information version can be maintained while maintaining the consistency of the database in a relatively loose operation. Management can be performed appropriately and efficiently.

  In the database management systems according to the third and fourth embodiments, PLIB is used as the hierarchical content database 1420. However, the present invention is not limited to this, and a hierarchical database in which classification items are hierarchically defined. Any database can be used.

  The database management system, database management method, database registration request program, and database management program of the present invention are a database management system in which a plurality of registration processing servers that make a content information registration request to the database server are distributed on the network. It is suitable for a database management method, a database registration request program, and a database management program.

1 is an explanatory diagram showing a network configuration of a database management system according to a first exemplary embodiment; 2 is a block diagram showing a functional configuration of an application server 100. FIG. 2 is a block diagram showing a functional configuration of a database server 110. FIG. It is explanatory drawing which shows an example of the structure of the dictionary of the content database. 10 is a flowchart illustrating a procedure of processing for making a registration request to the database server 110 of the content to be registered edited by the editing unit. 4 is a flowchart showing a procedure of version update processing by a version update unit 302 of the database server 110. FIG. 10 is an explanatory diagram showing a state in which content is edited by the Web browser 131 of the client terminal 130 in a flow from reading the content from the content database 120 to editing and registering the content in the content database 120. It is explanatory drawing which shows the flow of the process in which the content of the registration object received by application server 100a, 100b is transmitted to the database server 110, and is registered into the content database 120. FIG. It is explanatory drawing which shows the flow of a process which registers the content of registration 801 in the content database. It is explanatory drawing which shows the content database 120 of the state in which the content 801,802 with which the version was updated is registered. 4 is a flowchart showing a procedure of version update processing by a version update unit 302 of the database server 110. It is explanatory drawing which shows the flow of the process in which the content of the registration object received by application server 100a, 100b is transmitted to the database server 110, and is registered into the content database 120. FIG. It is explanatory drawing which shows the state by which the content 1201 was registered into the content database 120. FIG. It is a block diagram which shows the functional structure of the application server 1400 concerning Embodiment 2. FIG. It is a block diagram which shows the functional structure of the database server 1410 concerning Embodiment 2. FIG. It is explanatory drawing which shows an example of the process server table. 10 is a flowchart illustrating a procedure of processing for requesting registration to the database server 110 of the content to be registered edited by the editing unit. 15 is a flowchart showing a procedure for a registration request to the database server 1410 for content to be registered by the application server 1400. 10 is a flowchart showing a procedure of version update processing by a version update unit 1412 of the database server 1410. It is explanatory drawing which shows the state after reading a content from the content database 1420 until it stores in the acceptance queue 206 of the application server 1400a. FIG. 11 is an explanatory diagram showing a flow of processing in which registration target content 2000a is transmitted to the database server 110 and registered in the content database 1420. 12 is an explanatory diagram showing a flow of processing for registering content 2000b to be registered in a content database 1420. FIG. 10 is a flowchart showing a procedure of version update processing by a version update unit 1412 of the database server 1410. It is explanatory drawing which shows the flow of the process in which the content of the registration object received by application server 1400a, 1400b is transmitted to the database server 110, and is registered into the content database 120. FIG. It is explanatory drawing which shows the content of the final content database 1420. FIG.

Explanation of symbols

100, 100a, 100b Application server 110 Database server 120 Content database 126 Acceptance queue 130, 130a, 130b Client terminal 131 Web browser 140 Internet 150 Network 201 Editing unit 202 Registration accepting unit 203 Time information adding unit 204 Checkout unit 205 Transfer unit 206 Accepting queue 301 Receiving unit 302 Version updating unit 303 Registration unit 801, 802 Content 1201, 1202 Content 1400, 1400a, 1400b Application server 1401 Processing server table 1402 Dispatch unit 1403 Registration receiving unit 1410 Database server 1412 Version updating unit 1420 Content database 2000a, 2000b content

Claims (17)

A database server that manages a database in which content information including content and a version of the content is registered; and a request for registration of the content information from a client terminal device connected via a network; and the network server connected to the database server via the network A database management system having a plurality of registration processing servers that request registration of the content information received to the database server in the database,
Each of the plurality of registration processing servers includes:
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. Checkout means for transmitting to the client terminal device;
Editing means for receiving editing information indicating editing contents for the registered content information from the client terminal device, and editing the registered content information based on the received editing information to generate content information to be registered When,
Time information giving means for giving time information indicating current time to the content information to be registered edited by the editing means;
Transfer means for transmitting the content information to be registered, to which the time information is given by the time information giving means, to the database server;
The database server is
Storage means for storing a database in which the content information is registered;
Receiving means for receiving the content information to be registered, to which the time information is given from each of the plurality of registration processing servers;
Among the content information already registered in the database, the registered content that has the same search key as the registration target content information received by the receiving unit and has a newer version than the registration target content information. If information exists, version update means for updating the version of the content information to be registered and the version of the registered content information based on the time information;
Registration means for registering in the database the content information to be registered whose version has been updated by the version update means;
A database management system characterized by comprising: The version update means includes
Among the content information already registered in the database, the registered content that has the same search key as the registration target content information received by the receiving unit and has a newer version than the registration target content information. When the information exists, the version of the content information to be registered and the version of the registered content information are updated so as to become a newer version in the early order of the time information, and already registered in the database. In the content information, when the registration target content information received by the receiving unit is the same as the search key, and the registered content information whose version is newer than the registration target content information does not exist, The version of the content information to be registered The database management system of claim 1, characterized in that updating to a new version. The version update means has the same search key as the registration target content information received by the reception means, and the version is higher than the registration target content information, among the content information already registered in the database. When the new registered content information exists, the content information with the oldest time information is updated to the latest version among the version of the content information to be registered and the version of the registered content information. The database management system according to claim 1.   The version update means further deletes content information other than the content information with the oldest time information from the database among the version of the content information to be registered and the version of the registered content information. The database management system according to claim 3.   The version update means further has a search key identical to the content information to be registered received by the receiving means, and the content information already registered in the database, and from the content information to be registered 5. The database management system according to claim 3, wherein when there is no registered content information with a new version, the version of the content information to be registered is updated to a newer version. Each of the plurality of registration processing servers includes:
A first-in first-out acceptance queue that can retrieve data in the order of data storage;
Registration acceptance means for storing, in the acceptance queue, the content information to be registered, to which the time information is given by the time information giving means,
6. The transfer unit according to claim 1, wherein the transfer unit acquires the content information to be registered from the head of the acceptance queue, and transmits the acquired content information to be registered to the database server. The database management system according to one. A database server that manages a hierarchical database in which content information including a hierarchical structure classification item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content is registered; A plurality of registrations for receiving a registration request for the content information from a client terminal device connected via a network, and requesting registration of the content information received by the database server connected to the database server via the network A database management system having a processing server,
Each of the plurality of registration processing servers includes:
Processing server information storage means for storing processing server information that associates the classification items with identification information of registration processing servers that collectively perform registration requests for the content information to be registered to the database server;
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. Checkout means for transmitting to the client terminal device;
Editing means for receiving editing information indicating editing contents for the registered content information from the client terminal device, and editing the registered content information based on the received editing information to generate content information to be registered When,
Dispatch means for transmitting the registration target content information edited by the editing means to the registration processing server corresponding to the classification item included in the registration target content information based on the processing server information;
Transfer means for transmitting the received content information to the database server when the content information to be registered is received from another registration processing server;
The database server is
Database storage means for storing a hierarchical database in which the content information is registered;
Receiving means for receiving the content information to be registered from each of the registration processing servers;
Among the content information already registered in the database, the registration target content information received by the receiving means is the same as the classification item search key, and the version is newer than the registration target content information. A version update unit that determines whether or not registered content information exists, and updates the content information to be registered or the version of the registered content information based on the determination result;
Registration means for registering in the database the content information to be registered whose version has been updated by the version update means;
A database management system characterized by comprising:   The version update means includes the content information already registered in the database, the content information to be registered received by the receiving means and the search key for the classification item are the same, and the content to be registered If the registered content information whose version is newer than the information exists, the version of the content information to be registered is updated to a newer version than the latest version of the registered content information, and already registered in the database The registered content information that has the same search key for the classification item as the registration target content information received by the receiving unit and whose version is newer than the registration target content information is If it does not exist, the registration target The database management system of claim 7, wherein updating the version Ceiling information to a newer version.   The version update means includes the content information already registered in the database, the content information to be registered received by the receiving means and the search key for the classification item are the same, and the content to be registered 8. The database management system according to claim 7, wherein when there is the registered content information whose version is newer than the information, the content information to be registered is deleted.   The version update means further includes, among the content information already registered in the database, the content information to be registered received by the receiving means and the search key for the classification item are the same, and the registration target 10. The database management system according to claim 9, wherein when there is no registered content information whose version is newer than the content information, the version of the content information to be registered is updated to a newer version. Each of the plurality of registration processing servers includes:
A first-in first-out acceptance queue that can retrieve data in the order of data storage;
Registration acceptance means for storing, in the acceptance queue, the content information to be registered to be transmitted from the own server to the database server,
11. The transfer unit according to claim 7, wherein the transfer unit acquires the registration target content information from the head of the acceptance queue, and transmits the acquired registration target content information to the database server. The database management system according to one. In a registration processing server that makes a registration request for content information including content and the version of the content, the registration request for the content information is received from a client terminal device connected via a network, and connected to the registration processing server via a network, The database server that manages the database that has registered the content information is requested to register the received content information in the database, and the database server receives the registration request and registers the content information in the database. A database management method for
In each of the plurality of registration processing servers,
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. A checkout step of transmitting to the client terminal device;
An editing step of receiving edit information indicating edit contents for the registered content information from the client terminal device, and editing the registered content information based on the received edit information to generate content information to be registered When,
A time information giving step for giving time information indicating a current time to the content information to be registered edited in the editing step;
A transfer step of transmitting the content information to be registered, to which the time information is given by the time information giving step, to the database server;
In the database server,
A receiving step of receiving the content information to be registered to which the time information is given from each of the plurality of registration processing servers;
Among the content information already registered in the database, the registered content that has the same search key as the registration target content information received in the reception step and has a newer version than the registration target content information. If the information exists, a version update step of updating the version of the content information to be registered and the version of the registered content information based on the time information;
A registration step of registering the registration target content information whose version is updated by the version update step in the database;
A database management method comprising: A registration processing server that makes a registration request for content information including a classification item having a hierarchical structure indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content, is connected via a network. The database of the content information received from a database server that receives a registration request for the content information from a client terminal device and is connected to the registration processing server via a network and manages a hierarchical database in which the content information is registered. A database management method for requesting registration to the database server and registering the content information in the database in response to the registration request in the database server,
In each of the plurality of registration processing servers,
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. A checkout step of transmitting to the client terminal device;
An editing step of receiving edit information indicating edit contents for the registered content information from the client terminal device, and editing the registered content information based on the received edit information to generate content information to be registered When,
A process in which the registration target content information edited in the editing step is associated with the classification item and the identification information of the registration processing server that collectively performs a registration request for the registration target content information to the database server A dispatch step for transmitting to the registration processing server corresponding to the classification item included in the content information to be registered, based on the server information;
A transfer step of transmitting the received content information to the database server when the content information to be registered is received from another registration processing server;
In the database server, a receiving step of receiving the content information to be registered from each of the registration processing servers;
Among the content information already registered in the hierarchical database, the registration target content information received by the receiving step is the same as the search key of the classification item, and the version is higher than the registration target content information. A version update step of determining whether or not new registered content information exists, and updating the content information to be registered or the version of the registered content information based on the determination result;
A registration step of registering the registration target content information whose version is updated by the version update step in the database;
A database management method comprising: The content information registration request including the content and the version of the content is received from the client terminal device connected via the network, and the database server which is connected via the network and manages the database in which the content information is registered is received. A database registration request program for requesting registration of content information in the database,
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. A checkout procedure to be transmitted to the client terminal device;
An editing procedure for receiving editing information indicating editing content for the registered content information from the client terminal device, and editing the registered content information based on the received editing information to generate content information to be registered When,
A time information giving procedure for giving time information indicating a current time to the content information to be registered edited by the editing procedure;
A transfer procedure for transmitting the content information to be registered, to which the time information is given by the time information grant procedure, to the database server;
Database registration request program that causes a computer to execute. Database management for registering the content information in the database in response to a request for registration of the content information from a registration processing server that requests registration of the content information in a database in which content information including content and the version of the content is registered A program,
A receiving procedure for receiving the content information to be registered to which the time information has been given from the registration processing server;
Among the content information already registered in the database, the registered content that has the same search key as the content information to be registered received by the reception procedure and has a newer version than the content information to be registered If information exists, a version update procedure for updating the version of the content information to be registered and the version of the registered content information based on the time information;
A registration procedure for registering the content information to be registered whose version has been updated by the version update procedure in the database;
Database management program that causes a computer to execute. Accepts a request for registration of content information including a hierarchical classification item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content from a client terminal device connected via a network And a database registration request program for requesting registration of the content information to the database connected to the network and received from a database server that manages a database in which the content information is registered,
The content having the latest version from the content information registered in the database server is received from the database server, and information for editing the content information already registered in the database is generated using the content. A checkout procedure to be transmitted to the client terminal device;
An editing procedure for receiving editing information indicating editing content for the registered content information from the client terminal device, and editing the registered content information based on the received editing information to generate content information to be registered When,
A process in which the registration target content information edited by the editing procedure is associated with the classification item and the identification information of a registration processing server that collectively performs a registration request for the registration target content information to the database server A dispatch procedure to be transmitted to the registration processing server corresponding to the classification item included in the content information to be registered based on the server information;
A transfer procedure for transmitting the received content information to the database server when the content information to be registered is received;
A database registration request program that causes a computer to execute. Requests registration of the content information to a hierarchical database in which content information including a hierarchical structure item indicating content classification, an attribute corresponding to the classification item, an attribute value corresponding to the attribute, and a version of the content are registered. A database management program that receives a request for registration of the content information from a registration processing server and registers the content information in the hierarchical database;
A reception procedure for receiving the content information to be registered from the registration processing server;
Among the content information already registered in the hierarchical database, the registration target content information received by the reception procedure is the same as the search key of the classification item, and the version is higher than the registration target content information. A version update procedure for determining whether or not new registered content information exists, and updating the content information to be registered or the version of the registered content information based on the determination result;
A registration procedure for registering the content information to be registered whose version has been updated by the version update procedure in the database;
Database management program that causes a computer to execute.

Images