WO2009147704A1 - Programme d'édition en parallèle d'une table et d'éléments de table - Google Patents

Programme d'édition en parallèle d'une table et d'éléments de table Download PDF

Info

Publication number
WO2009147704A1
WO2009147704A1 PCT/JP2008/001719 JP2008001719W WO2009147704A1 WO 2009147704 A1 WO2009147704 A1 WO 2009147704A1 JP 2008001719 W JP2008001719 W JP 2008001719W WO 2009147704 A1 WO2009147704 A1 WO 2009147704A1
Authority
WO
WIPO (PCT)
Prior art keywords
item
editing
original
duplicate
computer
Prior art date
Application number
PCT/JP2008/001719
Other languages
English (en)
Japanese (ja)
Inventor
上村邦夫
Original Assignee
株式会社 アテナテレコムラボ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/JP2008/001424 external-priority patent/WO2008149552A1/fr
Priority claimed from PCT/JP2008/001506 external-priority patent/WO2009147701A1/fr
Application filed by 株式会社 アテナテレコムラボ filed Critical 株式会社 アテナテレコムラボ
Priority to JP2010515675A priority Critical patent/JPWO2009147705A1/ja
Priority to PCT/JP2008/001900 priority patent/WO2009147705A1/fr
Priority to PCT/JP2009/002501 priority patent/WO2009147851A1/fr
Priority to JP2010515778A priority patent/JP4855538B2/ja
Priority to US12/743,367 priority patent/US20110161292A1/en
Publication of WO2009147704A1 publication Critical patent/WO2009147704A1/fr
Priority to JP2010254885A priority patent/JP5543899B2/ja
Priority to US13/024,330 priority patent/US20110137862A1/en
Priority to US13/714,422 priority patent/US20130110777A1/en
Priority to US13/726,549 priority patent/US20130179652A1/en
Priority to US13/802,740 priority patent/US20130204842A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation

Definitions

  • the present invention relates to a computer program for editing a database in parallel by a plurality of computers.
  • table items are defined before entering a record.
  • a new table program using
  • Patent Document 4 has the same concept.
  • Patent Document 5 relates to a method for creating a new table.
  • Non-Patent Document 1 describes various DB software that can be operated with SQL statements, such as “Add new column to table” P384, “Change table column type” P389, “Delete table column” P395, etc. Explains the operation. In either case, the configuration of the table is changed by executing these instructions.
  • Patent Document 1 and Patent Document 2 show “a mechanism for resolving inconsistencies caused by editing table records in parallel by parallel database access”, but inconsistencies caused by editing table items. Does not show how to deal with it.
  • a table that defines the items of a table (hereinafter “original table”) is introduced. This is called an “item table”.
  • the item table is also subject to parallel editing. It is two. Details are shown below.
  • a copy (replica DB) of the original DB exists in a plurality of computers, the duplicate DB is edited in parallel by the plurality of computers, and the edited result is uploaded to the server.
  • the uploaded editing is determined to be valid or invalid by “determination of editing validity”, and the original DB of the server is updated with the effective editing, and the version of the original DB is updated.
  • the duplicate DB is updated by copying the updated original DB.
  • the version of the original DB is copied as the base version of the duplicate DB, that is, the version serving as the base for the next editing.
  • the above is “update of replication DB”. Copying the latest original DB and its version is called “synchronizing the duplicate DB” or simply “synchronizing”.
  • the server can also be operated simply by recording the edits performed on each computer and the order of their upload. The process is the same until the editing of the duplicate DB is uploaded to the server (when there is an original DB), but the update procedure of the duplicate DB thereafter is different.
  • the computer captures (downloads) up to the latest edits in the server in order, evaluates each edit by “determining the validity of the edit”, updates the duplicate DB with the edit determined to be valid, and updates the base version. Update. If the same editing is taken in, the duplicate DB of any computer is updated to the same content and the same base version. In other words, it can be said that the duplicate DB of each computer is "a duplicate of the virtual original DB”.
  • the update of the duplicate DB by taking in the edits from the server is also “update the duplicate DB”. Taking the latest edits and updating the duplicate DB is referred to as “synchronize the duplicate DB” or simply “synchronize”.
  • update of duplicate DB means both the case where the original DB is present and the case where the original DB is not present.
  • update replication table When attention is paid to editing of a specific table, it is referred to as “update replication table”, “synchronize replication table”, or simply “synchronize”.
  • the computer performs “judgment of editing validity” in order for the edits taken from the server, and that the editing being noticed in the process is judged to be valid. .
  • ⁇ A Relationship between item table and original table>
  • Each record in the item table defines an item in the original table.
  • the items in the original table are defined and displayed (or printed) according to the contents of each record in the item table.
  • the program displays (or prints) the items in the original table in the “display order” recorded in the item record.
  • the value of “display order” in the item record may be changed.
  • ⁇ B Parallel editing of item table>
  • the item table is also subject to parallel editing, but the specific mechanism differs depending on the version management method.
  • the item table and the original table will be described below in two cases: a case of “managing with one version number” and a case of “managing with another version number”.
  • the editing for the duplicate DB is uploaded to the server that manages the change together with the base version of the duplicate DB.
  • This base version can be used for “determination of editing effectiveness”.
  • the item table is edited and uploaded. This edit is only for editing the item table (record), not for the original table (record). Thereafter, confirmation of editing of this item table is confirmed. If it cannot be confirmed, the editing to the item table is abandoned and the configuration of the original table is not changed.
  • the configuration of the original table is changed based on this, and this editing is uploaded to the server together with the base version of the replication DB, and the editing is confirmed. If there is another modification to the record in the original table, this is done after this determination.
  • the old item may not exist or the old item may be unexpected There may be a situation in which the “conversion process” cannot be continued because the value of is set. One way to prevent this situation is to prohibit “conversion processing”.
  • the information held by the dummy edit 0906 includes a reference 0908 to the base “item (table) edit” 0905 and “base version (number) of duplicate DB of original table” at the time of editing the item table. It consists of the designation 0907.
  • the validity of the dummy edit 0906 uploaded as an edit to the original table is determined using the “base version (number) of the duplicate DB of the original table” recorded therein.
  • the determination is made based on the criteria of “validate editing to a new DB with a new base version number” and “validate the first base version number that has been uploaded earlier”.
  • the dummy edit 0906 becomes invalid, the corresponding “item (table) edit” 0905 is also invalidated.
  • the item edit 0905 becomes invalid, the corresponding dummy edit 0906 is also invalidated.
  • FIG. This is composed of two (terminal) computers (computer A 0101 and computer B 0102) and a server 0103, which are connected via a communication network 0104 such as the Internet.
  • the computer A 0101 and the computer B 0102 first copy the initial DB 0105 in the server 0103 to create a duplicate DB.
  • the computer edits (adds, corrects, deletes) each replica DB, and uploads the correction contents to the server.
  • “Edit (1)” 0106 and “edit (2)” 0107 are the records.
  • a computer is generally configured by connecting a computing device, a main storage device, a secondary storage device, an input / output device, a communication device, a display device, and the like via a bus.
  • the computer A 0101 and the computer B 0102 in FIG. 1 read the program of the present invention, and each computer functions as a collection of means shown in FIG.
  • the computer 0201 connects to a communication network 0202 such as the Internet through the communication means 0203 and communicates with the server 0210 beyond that.
  • the tables that are the targets of these operations are both the item table and its original table. Although it is a natural embodiment that the entire database is the target of operation, it is sufficient for the present invention to limit to the item table of interest and its original table.
  • the initial DB 0105 in the server is copied to be a duplicate DB of the computer. If there is no duplicate DB in the computer, this operation is first performed. Note that it is sufficient for the present invention to create a replica of the table of interest (item table and original table) without creating a replica of the entire DB.
  • FIG. 3 shows a procedure for successively executing “means for creating a copy (replication table) of a table original (original table)” 0204 and “a means for synchronizing a replication table with the latest (virtual) original table” 0205. Shown in First, it is investigated 0301 whether a “replication table” of a copy of the original table has been created in the computer. If there is not, a duplicate table is created 0302 by copying the original table in the initial DB. Copying the entire initial DB to create a replica DB does not change the target replica table.
  • This computer participates in parallel editing of DBs by “means for editing a replication table” 0206. Not only the original table, but also the item table. These editing results are uploaded to the server by “means for uploading the replication table editing result to the server” 0207. This procedure is shown in FIG. First, “specify editing result” 0401, “specify the base version of the replication table (or replication DB) to be edited in the editing result” 0402, and upload the edit 0403 to the server.
  • the base version of the replication table (replication DB) to be edited is the version number specified in the original table (original DB) of this replication table (replication DB), and is updated by editing determined to be valid. . If a version (number) is specified in the original DB (or virtual original DB), this version is updated each time a partial correction of the duplicate DB is updated, and this is used as a base version of the duplicate DB copied. Used.
  • this version is updated each time the copy table is updated, and is used as the base version of the copy table.
  • the uploaded edits are taken into the other computer by “means to synchronize the duplicate table with the latest (virtual) original table” 0205 of the other computer, and “determination of editing validity” 0303 is performed.
  • the replication table (replication DB) of the computer is updated.
  • the “means for synchronizing the duplicate table with the latest (virtual) original table” 0205 is also executed by the computer that has uploaded this edit, and “determination of editing validity” 0303 is performed.
  • the flow of processing is shown in FIG. First, the presence / absence of “addition” or “real deletion” of the record in the item table is confirmed 0501. If there is an “add” or “true delete”, an empty original table with a new item structure is created 0502. Then, the old original table record is extracted 0503, and its contents are transferred to the new original table 0504. If an item is “really deleted”, its value cannot be transferred (cannot be transferred) to the new source table.
  • the DB software to be used has an item editing function and the configuration of the table is changed with the item editing, this may be used.
  • “means for reconstructing the replication table based on the contents of the replication item table” 0208 is realized by calling an item editing function of the DB software based on the content of the replication item table.
  • conversion processing that is, “processing for setting a new item value based on the value of an existing item” is specified, “retrieve the old source table record” in FIG. After the “transfer to table” 0504 process, the designation of the conversion process is confirmed and 0505 is executed, or “conversion process” is executed 0506 in the middle of these processes.
  • conversion process Example A specific example of the conversion process is shown in “Conversion Process Example” of the first embodiment.
  • Example 1 shows a case where the item table and the original table are recorded in the same DB, and both the item table and the original table are managed by this DB version.
  • the original table 0702 in FIG. 7 and the item table 0701 are recorded in the same DB.
  • records of student names, evaluations, and entrance dates are recorded as records defining the items in the original table.
  • Two records are recorded in the original table.
  • the original table is displayed on a computer screen or the like as “first display” 0703.
  • a “conversion process” from a conventional “evaluation” value to a new “evaluation” is defined. For example, 0 to 59 is “failed”, 60 to 100 is “passed”, other numbers, characters that cannot be converted to numbers, and unfilled are “undecided”.
  • the computer A 0802 and the computer B 0803 acquire the initial DB 0804 0807 and 0808, respectively, and use them as the duplicate DB 0805 and 0806, respectively. Since the initial DB 0804 of version 0 of the server 0801 is copied, the base version is 0 for both. After that, edit 1 to edit 6 are uploaded to the server 0801. This is an edit that has been uploaded by a computer other than computer A0802 and computer B0803.
  • the synchronization 0809 is performed as the first process.
  • edit 1 to edit 6 are acquired from the server 0801, and the base version of the duplicate DB 0805 is set to 6.
  • the item table in the duplicate DB 0805 is edited 0810.
  • the edited result is uploaded to the server and recorded as 0811 and edited 7.
  • the computer A0802 reconstructs the original table and sends the result to the server as an edit. 0814.
  • This editing is editing 8 on the server.
  • Computer A 0802 receives this confirmation, synchronizes the duplicate DB 0815, and displays this to the operator of computer A 0802 0816. Then, the computer B 0203 synchronizes the duplicate DB 0806 with the (virtual) original DB 0817.
  • the edit uploaded from the computer B 0803 is validated and one (base) version is updated on the basis of “validate the one that was uploaded first if the same base version number”.
  • Up 0814 from the previous computer A 0802 is invalidated by “determination of validity of editing”.
  • the version is unconditionally updated each time editing is performed, and two or more versions are updated from the base version of editing. There is also a method of determining invalidity when it is done.
  • criteria for determining the effectiveness of editing There are other variations of the criteria for determining the effectiveness of editing. For example, “prioritize editing with an old editing time” and “validate new editing for the same record” are examples of criteria for determining the validity of editing, regardless of the validity of the determination.
  • FIG. 9 shows a transition example of the original version of the original table 0901 and the item table 0902 or the base version of the copy.
  • the vertical axis is the time axis, and time passes from top to bottom.
  • the initial version of both tables is zero.
  • the item edit is also retroactively processed. Note that in order to invalidate the item editing retroactively, it is necessary to save the state before the item editing until the dummy editing 0906 is determined to be valid.
  • the configuration change of the original table is performed in accordance with the contents of the item edit 0905, and it is uploaded and determined to be valid. And the version of the original table is 4.
  • the configuration change 0909 mentioned above is effective in “determination of editing validity”.
  • Parallel DB access in which the original database (hereinafter referred to as DB) is copied to a plurality of computers to create a duplicate DB, the duplicate DB is edited in parallel with the plurality of computers, and the result is reflected in the original DB.
  • table items can now be edited. Realization of parallel DB access means that DB processing can be continued even in a situation where connection to a server is impossible. Since table items can be added, deleted, and changed, a large degree of freedom is given to DB operation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention porte sur une méthode d'accès en parallèle à une base de données selon laquelle l'original de la base de données (ci-après dite BD) est copié dans plusieurs ordinateurs pour y créer un duplicata de la BD. La BD reproduite est édité par les ordinateurs en parallèle et le résultat est reflété dans la BD originale; les tables sont éditées en parallèle et une table qui définit les éléments des tables est également retenue pour l'édition en parallèle. Après confirmation de l'édition d'une table d'éléments par l'intermédiaire de la validation de l'édition, la table d'éléments exécute si nécessaire la reconstruction de la table originale définissant les éléments. Cela permet non seulement l'édition en parallèle de contenus de table, mais aussi l'édition d'adjonctions, de suppressions ou de modifications ou analogues d'un élément d'une table et le partage du résultat entre les ordinateurs.
PCT/JP2008/001719 2007-06-06 2008-07-01 Programme d'édition en parallèle d'une table et d'éléments de table WO2009147704A1 (fr)

Priority Applications (10)

Application Number Priority Date Filing Date Title
JP2010515675A JPWO2009147705A1 (ja) 2008-06-04 2008-07-15 データベース接続プログラムおよび装置
PCT/JP2008/001900 WO2009147705A1 (fr) 2008-06-04 2008-07-15 Programme et dispositif de connexion de bases de données
PCT/JP2009/002501 WO2009147851A1 (fr) 2008-06-04 2009-06-03 Procédé pour éditer en parallèle des éléments de données d'une base de données
JP2010515778A JP4855538B2 (ja) 2008-06-04 2009-06-03 データベースのデータ項目の平行編集方式
US12/743,367 US20110161292A1 (en) 2007-06-06 2009-06-03 Method for parallel editing data item of database
JP2010254885A JP5543899B2 (ja) 2008-06-04 2010-11-15 データベースのデータ項目の平行編集方式
US13/024,330 US20110137862A1 (en) 2008-06-12 2011-02-10 Method and apparatus for parallel edit to editable objects
US13/714,422 US20130110777A1 (en) 2007-06-06 2012-12-14 Synchronization of data edited in parallel
US13/726,549 US20130179652A1 (en) 2007-06-06 2012-12-25 Support for synchronization of data edited in parallel
US13/802,740 US20130204842A1 (en) 2007-06-06 2013-03-14 Method and system for synchronization of data edited in parallel

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
PCT/JP2008/001424 WO2008149552A1 (fr) 2007-06-06 2008-06-04 Procédé de solution de contradiction de la base de données
JPPCT/JP2008/001424 2008-06-04
PCT/JP2008/001506 WO2009147701A1 (fr) 2008-01-08 2008-06-12 Programme d’accès parallèle de base de données
JPPCT/JP2008/001506 2008-06-12

Publications (1)

Publication Number Publication Date
WO2009147704A1 true WO2009147704A1 (fr) 2009-12-10

Family

ID=41397796

Family Applications (5)

Application Number Title Priority Date Filing Date
PCT/JP2008/001719 WO2009147704A1 (fr) 2007-06-06 2008-07-01 Programme d'édition en parallèle d'une table et d'éléments de table
PCT/JP2008/001900 WO2009147705A1 (fr) 2008-06-04 2008-07-15 Programme et dispositif de connexion de bases de données
PCT/JP2009/002490 WO2009147846A1 (fr) 2007-06-06 2009-06-03 Système de résolution de conflits pour l'édition de bases de données en parallèle
PCT/JP2009/002501 WO2009147851A1 (fr) 2007-06-06 2009-06-03 Procédé pour éditer en parallèle des éléments de données d'une base de données
PCT/JP2009/002491 WO2009147847A1 (fr) 2007-06-06 2009-06-03 Méthode d'édition de bases de données en parallèle

Family Applications After (4)

Application Number Title Priority Date Filing Date
PCT/JP2008/001900 WO2009147705A1 (fr) 2008-06-04 2008-07-15 Programme et dispositif de connexion de bases de données
PCT/JP2009/002490 WO2009147846A1 (fr) 2007-06-06 2009-06-03 Système de résolution de conflits pour l'édition de bases de données en parallèle
PCT/JP2009/002501 WO2009147851A1 (fr) 2007-06-06 2009-06-03 Procédé pour éditer en parallèle des éléments de données d'une base de données
PCT/JP2009/002491 WO2009147847A1 (fr) 2007-06-06 2009-06-03 Méthode d'édition de bases de données en parallèle

Country Status (2)

Country Link
JP (1) JPWO2009147705A1 (fr)
WO (5) WO2009147704A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8171003B2 (en) 2007-06-06 2012-05-01 Kunio Kamimura Method and apparatus for changing reference of database
JP5356351B2 (ja) * 2010-09-30 2013-12-04 ヤフー株式会社 ストレージサーバ、ファイル同期システム、ファイル衝突処理方法及びプログラム
US9946691B2 (en) * 2013-01-30 2018-04-17 Microsoft Technology Licensing, Llc Modifying a document with separately addressable content blocks
WO2015009688A1 (fr) 2013-07-17 2015-01-22 The Johns Hopkins University Puce microfluidique pour analyse de motilité cellulaire et méthodes d'utilisation associées
CN106156094B (zh) 2015-04-01 2019-09-17 阿里巴巴集团控股有限公司 一种数据库的远程数据同步方法和装置
CN111523291B (zh) * 2020-04-21 2023-04-18 四川川大智胜软件股份有限公司 一种低空雷达多席位空域数据编辑方法
JP7475086B1 (ja) 2023-02-03 2024-04-26 株式会社ミヤワキ 編集方法、編集装置及びプログラム

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11272533A (ja) * 1998-03-25 1999-10-08 Fujitsu Ltd リレーショナルデータベース同期方法およびそのプログラムを記録した記録媒体
JP2000194592A (ja) * 1998-12-25 2000-07-14 Nippon Telegr & Teleph Corp <Ntt> デ―タベ―スシステム、デ―タベ―スアクセスシステム、およびデ―タベ―スアクセスプログラムを記録した記録媒体

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05233405A (ja) * 1992-02-18 1993-09-10 Hitachi Ltd データベース変更監視方式
JPH07191898A (ja) * 1993-12-27 1995-07-28 Fujitsu Ltd データベース排他制御装置
CA2152528C (fr) * 1994-07-29 2000-04-18 Chung-Hwa Herman Rao Systeme reparti a fichiers repetes
JP3534596B2 (ja) * 1997-12-05 2004-06-07 富士通株式会社 インテリジェントネットワーク内のデータベースの同期方法と装置
JP2000020370A (ja) * 1998-06-29 2000-01-21 Sharp Corp データ同期処理装置
JP2000222268A (ja) * 1999-01-29 2000-08-11 Hitachi Ltd 複数のコンピュータ間におけるファイルの同期方法
JP2000284998A (ja) * 1999-03-31 2000-10-13 Ricoh Co Ltd データ更新制御システム、データ更新制御方法、その方法を実行させるためのプログラムを記録したコンピュータ読み取り可能な記録媒体
US6938070B2 (en) * 2001-12-17 2005-08-30 Dassault Systemes Conflict resolution for collaborative work system
JP4279499B2 (ja) * 2002-03-01 2009-06-17 シャープ株式会社 情報処理装置
JP2007179105A (ja) * 2005-12-26 2007-07-12 World Planning:Kk 共有データベースの制御システム及び共有データベースの制御方法並びにコンピュータプログラム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11272533A (ja) * 1998-03-25 1999-10-08 Fujitsu Ltd リレーショナルデータベース同期方法およびそのプログラムを記録した記録媒体
JP2000194592A (ja) * 1998-12-25 2000-07-14 Nippon Telegr & Teleph Corp <Ntt> デ―タベ―スシステム、デ―タベ―スアクセスシステム、およびデ―タベ―スアクセスプログラムを記録した記録媒体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TAKASHI SHIKII: "C++Builder Database Programming Dai 2 Kai", INSIDE WINDOWS, vol. 3, no. 12, 1 December 1997 (1997-12-01), pages 71 - 77 *

Also Published As

Publication number Publication date
WO2009147851A1 (fr) 2009-12-10
WO2009147847A1 (fr) 2009-12-10
JPWO2009147705A1 (ja) 2011-10-20
WO2009147705A1 (fr) 2009-12-10
WO2009147846A1 (fr) 2009-12-10

Similar Documents

Publication Publication Date Title
US11561956B2 (en) Key pattern management in multi-tenancy database systems
JP4573277B2 (ja) データベース矛盾解消方式
CN110147369B (zh) 多重租赁数据库系统中的数据分离和写入重新定向
WO2009147704A1 (fr) Programme d&#39;édition en parallèle d&#39;une table et d&#39;éléments de table
US10482080B2 (en) Exchanging shared containers and adapting tenants in multi-tenancy database systems
CN109947767B (zh) 多重租赁数据库系统中的系统共享类型
CN109947773A (zh) 在多租户数据库系统中部署对键模式的改变
JP2022141841A (ja) 分散型台帳を用いて公共のソフトウェアコンポーネント・エコシステムを管理するためのシステムおよび方法
US20010011265A1 (en) Method and apparatus for deploying data among data destinations for website development and maintenance
US20070288835A1 (en) Apparatus, computer readable medium, data signal, and method for document management
TW200842627A (en) Techniques to cross-synchronize data
EP4189914B1 (fr) Utilisation de multiples chaînes de blocs pour appliquer des transactions à un ensemble d&#39;objets de données persistants dans des systèmes de stockage persistants
JP4497691B2 (ja) データベース管理方法及び管理システム
JP2002108681A5 (fr)
JP2001306372A (ja) 文書管理方法およびその方法を実施するためのプログラムを記憶した記憶媒体
CN114741453A (zh) 数据同步的方法、系统及计算机可读存储介质
JP5543899B2 (ja) データベースのデータ項目の平行編集方式
JP2003281118A (ja) 文書管理装置、文書編集装置、文書管理方法、文書編集方法及びプログラム
CA2388772A1 (fr) Procede et dispositif de deploiement de donnees vers des destinations de donnees pour la mise au point et la maintenance de sites web
US20170177647A1 (en) Parallel database editing
JP4855538B2 (ja) データベースのデータ項目の平行編集方式
JP2000132435A (ja) 異種データベース管理システム間のデータ整合処理装置
Conte et al. Integration of an active research data system with a data repository to streamline the research data lifecycle: Pure-NOMAD case study
JPWO2009147846A1 (ja) データベース並行編集の競合解消方式
Gupta Mastering Oracle GoldenGate

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08790118

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08790118

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP