- Logged replication: Directory for creating the files required by the replication and by the log process
HCreateSubscriberReplica (Function) In french: HCréeRéplicaAbonné
 Available only with these kinds of connection
Creates the description file of a subscriber replica. The extension of the file corresponding to the subscriber replica is .RPL. This function can be used with the logged replication and/or with the universal replication Caution: When creating a subscriber replica, you must: Remark: The replication is not available when accessing a database via Remote access. Remark: From version 19, HFSQL is the new name of HyperFileSQL. Versions 22 and later New in version 22Syntax
Universal replication Hide the details
<Result> = HCreateSubscriberReplica(<Directory of master replica> , <Directory of subscriber replica> , <Identifier> , <Size of range of identifiers> , <List of tables to replicate>)
<Result>: Integer - Identifier of Subscriber Replica that was created,
- 0 if no subscriber replica was created.
<Directory of master replica>: Character string (with quotes) Directory where the description file of Master Replica (RPM file) was created (HCreateMasterReplica). This directory can be a network directory or a UNC path. If this parameter corresponds to an empty string (""), the description file will be sought in the current directory of HFSQL data files (defined in the data model editor or by programming). Caution: This directory must be accessible when running HCreateSubscriberReplica. <Directory of subscriber replica>: Character string (with quotes) Directory where the description file of Subscriber Replica must be created. This file is named Replica_<Identifier>.RPL. If this parameter corresponds to an empty string (""), the description file will be created in the current directory of HFSQL data files (defined in the data model editor or by programming). <Identifier>: Integer or character string Identifier of the subscriber replica. This identifier will be used by HCreateMoveableReplica. A WLanguage error occurs if the specified identifier already exists. <Size of range of identifiers>: Integer This parameter is ignored. <List of tables to replicate>: Character string This list has the following format:
<TableName>[+TAB+<NameDateItem>][+<CR>+<TableName>[+TAB+<NameDateItem>]]...
Caution: The order of the tables is important. The order of the tables is the order of the dependencies for the tables. If the records of file 1 are linked to the records of file 2 and if the record must be found in file 2 in order for the addition in file 1 to comply with the integrity rules, then file 1 must be positioned first in the list. For example, for the "Customer", "Orders" and "Order line" files (that are linked by links whose cardinalities are (0,n) - (1,1)), the "Customer" file must be positioned first (a customer must exist to add an order), then the "Orders" file (an order must exist to add an order line) and finally the "Order line" file. The name of Date item is mandatory for the databases not in HFSQL format. This item must correspond to an item of the data file updated during an addition or during a modification. This operation must be performed by the application. Business / GUI classification : Business Logic
This page is also available for…
|
|
|