Abstract: Consistency of replicated data copies with statement-based replication is provided without requiring transaction serializability. At a subordinate replication node, a transaction start message, replicated data modification statements, and a transaction commit message are received for a next committed transaction from a master replication node, wherein the transaction start message carries a master transaction identifier, an invisibility list consisting of identifiers of other master transactions that had started and not yet committed when this master transaction started, and an earliest invisible master transaction identifier. The master transaction identifier, invisibility list, and earliest invisible transaction identifier are mapped to subordinate transaction identifiers to preserve an order of transaction identifiers from the master replication node.

Abstract: Consistency of replicated data copies with statement-based replication is provided without requiring transaction serializability. At a subordinate replication node, a transaction start message, replicated data modification statements, and a transaction commit message are received for a next committed transaction from a master replication node, wherein the transaction start message carries a master transaction identifier, an invisibility list consisting of identifiers of other master transactions that had started and not yet committed when this master transaction started, and an earliest invisible master transaction identifier. The master transaction identifier, invisibility list, and earliest invisible transaction identifier are mapped to subordinate transaction identifiers to preserve an order of transaction identifiers from the master replication node.

Abstract: Consistency of replicated data copies with statement-based replication is provided without requiring transaction serializability. At a subordinate replication node, a transaction start message, replicated data modification statements, and a transaction commit message are received for a next committed transaction from a master replication node, wherein the transaction start message carries a master transaction identifier, an invisibility list consisting of identifiers of other master transactions that had started and not yet committed when this master transaction started, and an earliest invisible master transaction identifier. The master transaction identifier, invisibility list, and earliest invisible transaction identifier are mapped to subordinate transaction identifiers to preserve an order of transaction identifiers from the master replication node.

Abstract: Consistency of replicated data copies with statement-based replication is provided without requiring transaction serializability. At a subordinate replication node, a transaction start message, replicated data modification statements, and a transaction commit message are received for a next committed transaction from a master replication node, wherein the transaction start message carries a master transaction identifier, an invisibility list consisting of identifiers of other master transactions that had started and not yet committed when this master transaction started, and an earliest invisible master transaction identifier. The master transaction identifier, invisibility list, and earliest invisible transaction identifier are mapped to subordinate transaction identifiers to preserve an order of transaction identifiers from the master replication node.

Abstract: A system and method of relationship management for data modeling in an integrated development environment is provided. A method of incorporating a program code file includes generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.

Abstract: A method of validating a relationships table. The method includes generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema including two related tables. The method further includes determining a relationship between the two tables. Further, the method includes adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols. Additionally, the method includes producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set. Furthermore, the method includes generating the relationships table in the relational schema containing the relationship between the two tables.

Abstract: A system and method of relationship management for data modeling in an integrated development environment is provided. A method of incorporating a program code file includes generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.

Abstract: A process flow development tool is given a capability of determining the properties corresponding to a particular type of object and allowing a user to decide how and where the properties will be shown in a Properties dialog for individual objects of the particular type. The capability allows the tool to present a dialog that allows the user to customize, for the particular type of object, the layout for the properties in the Properties dialog. This layout may then be stored in an organizer object associated with the particular type of object.

Abstract: A system and method of relationship management for data modeling in an integrated development environment is provided. A method of incorporating a program code file includes generating a relational schema of symbols in the program code file based on a framework for models in the integrated development environment, the schema comprising at least two related tables; determining a relationship between the at least two tables in the relational schema; adding definitions from the program code file for symbols in the relational schema to a definition set retaining definitions of symbols; and producing proxy definitions for use with the definition set for each symbol in the program code file without a definition in the definition set.

Abstract: There is provided a method and system for developing a transformation program to transform a data structure from a first format to a second format, the program including a plurality of coupled data transformation modules describing the transformation, the method comprising the steps of: generating a first transformation module of the plurality of transformation modules for assembling the program, the first module being a module type of a set of module types including a language constructed module type and a visually constructed module type; extracting reference information from the first module for accessing the first module when stored in a memory; and updating a module registry to include a first entry corresponding to the reference information of the first module, the module registry configured for having reference information entries extracted from both the language constructed modules and visually constructed modules.

Abstract: There is provided a system and method for deploying a set of coupled data transformation modules describing a data transformation, the data transformation for transforming a data structure from a first format to a second format, the method including the steps of receiving an instruction for selecting the set of transformation modules from a memory; converting each of the set of transformation modules to a common model format, the set of modules having at least one transformation module being of a module type of a type set including language constructed modules and visually constructed modules; and generating an executable version of the converted transformation modules suitable for execution by a data transformation engine; wherein the executable version when executed transforms the data structure from the first format to the second format.

Abstract: A process flow development tool is given a capability of determining the properties corresponding to a particular type of object and allowing a user to decide how and where the properties will be shown in a Properties dialog for individual objects of the particular type. The capability allows the tool to present a dialog that allows the user to customize, for the particular type of object, the layout for the properties in the Properties dialog. This layout may then be stored in an organizer object associated with the particular type of object.

Abstract: A metadata repository for use in an integrated development environment is provided. The metadata repository is layered to define levels of common behaviour useful to different types of application development tools. The most general use tools have access to metadata at the level of simple constructed types; more specialised tools have access to components that contain properties of a target language; highly specialised tools have access to composed partitionable part metadata that can be used for constructing distributed applications.