ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / WLanguage / Managing databases / HFSQL / Types of HFSQL variables
  • Properties specific to hRSConfig variables
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
The hRSConfig type is used to define the advanced characteristics of a replication between 2 HFSQL servers. The characteristics of this replication can be defined and modified using various WLanguage properties.
Note: For more details on the declaration of this type of variable and the use of WLanguage properties, see Declaring a variable.
Example
Cnx is Connection
ConfigRéplication1 is hRSConfig

ConfigRéplication1.Server = "atlas.masociete.com:4996"
Add(ConfigRéplication1.File, "Mabase")
Add(ConfigRéplication1.File, "-Mabase\Monfichier.fic")
HRSAddConfig(Cnx, ConfigRéplication1, hrsNoCopy)
Properties

Properties specific to hRSConfig variables

The following properties can be used to handle a replication between HFSQL servers:
Property nameType usedEffect
BidirectionalBoolean
  • True if replication is required in both directions: replication will be bi-directional.
  • False otherwise (default value): replication will be unidirectional.
DescriptionCharacter stringDescription of replication.
FileArray of stringsList of elements to replicate.
The elements to replicate can correspond to:
  • a database,
  • a data file,
  • a data file to exclude from the replication. In this case, the name of the file must be prefixed by "-" (minus).
IdentifierentierUsed to identify the replication handled.
This property is read-only.
IdentifierOpposedentierIn the case of bidirectional replication, corresponds to the replication identifier from the opposite server to the replicated server..
This property is read-only.
InitializationentierUsed to follow the evolution of the initial copy of replicated elements from the connection server (master server) to the other server (subscriber server) during a copy in background task (HRSAddConfig associated with the hrsCopyBackgroundTask constant).
If this property:
  • is included between 0 and 1000, the replication is currently added.
  • is set to 1000, the replication was added.
  • is not specified, the replication failed to be added.
This property is read-only.
ModificationConflictResolutionInteger constantMethod for solving the conflicts:
  • hrcmPlusPriority (default): In the event of a conflict, only the priority value defined for the server is taken into account. The smaller the priority value defined for the server is, the higher the priority granted to the server will be.
  • hrcmPlusRécent: In the event of a conflict, the most recent element takes precedence.
    Caution: This method requires synchronization of the clocks on the different servers..
  • hrcmProcedureWithModifiedRubrics: When a conflict occurs, a stored procedure is launched (defined by the property ProcedureResolutionConflictModification). In this procedure, only the modified items will be accessible.
  • hrcmProcedureAllRubrics: When a conflict occurs, a stored procedure is launched (defined by the property ProcedureResolveConflictModification).. In this procedure, all the items found in the record will be accessible.
PasswordCharacter stringPassword specific to the replication. This password must correspond to the password specified in HRSInit used on the subscriber server.
This property is available in write mode.
ProcedureForModificationConflictResolutionCharacter stringName of the stored procedure to be used if the conflict resolution method (ModificationConflictResolution) corresponds to the hmcrProcedureWithModifiedItems or hmcrProcedureAllItems constants.
This stored procedure must return:
  • the opRetry constant to validate the replication of the modification,
  • the opCancel constant to cancel the replication of the modification.
This stored procedure must be found in the replicated database on the subscriber server.
SchedulinghScheduling variableReplication period.
If all the members of the hScheduling variable are left empty, it will be a replication in streaming.
ServerCharacter stringTarget server of the replication. This server is identified by:
  • its DNS name or its IP address.
  • the replication port (4996 by default).
If the port differs from the default port, the following syntax must be used to specify it: "<Server name>:<Replication port>". This port must correspond to the port specified in HRSInit used on the subscriber server.
SpareBoolean
  • True to perform a replication in spare mode,
  • False otherwise.
Note: This property is incompatible with the Bidirectionalproperty. .
Minimum version required
  • Version 18
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 09/19/2024

Send a report | Local help