COPYCAT

Version 3.01.0 (17th of March 2011)

• Addeed support for Embarcadero RAD Studio XE.
   
• Fixed the default transaction parameter setting for FIBPlus, which sometimes caused problems on Firebird 2.1.
   
• Added support for Firebird 2.5.
   
• Added support for accessing record data from within a synchronisation statement. Using the keyword "new." will result in the field data from the row to be synchronized.
  
  
• Added a new connector for Zeos.
  
  
• Added a password in RPL$USERS for transport connection. This password is used for authenticating replication clients connecting to remote CopyCat servers (PHP or Java). It is not used for replication over a direct connection, as in such cases, only the database connection parameters are needed.
   
• Added property TCcReplicator.TableMapping, allowing replication to occur between tables with the same structure but different table names on the local and remote databases.
  
  
• New BatchImport function, allowing for fast, punctuel synchronisation of data based on an SQL condition.
   
• Two fields added to RPL$CONFLICTS, SQL1 and SQL2, to indicate the current field values of the conflictual row on both nodes. This makes it easy to compare the row on both nodes to determine which one to keep. 
  
  
• Added new table RPL$TRACE, which holds a trace of all data-changing SQL (INSERT/UPDATE/DELETE) executed during replication. This tracing can be turned on or off based on a new property of TCcReplicator called TraceType.
  
  
• Added compilation option {$DEFINE CC_MEMDS_KBM} (in CC.INC) which if activated compiles CopyCat to internally use TkbmMemTable instead of the built-in memory dataset (which is still used by default). kbmMemTable must be installed for this option to work. This should allow better performance, particularly for large sets of data.
  
  
• Added a new property in TCcReplicator called AutoPriority. If this property is enabled, CopyCat will use the operation dates recorded in RPL$LOG to order the rows according to the order they occured in, rather than according to a preconfigured priority setting. This makes the order of events more logical and easier to follow, as well as averting the need to configure the priorities of all the tables. There may be situations where manually setting priorities will still be necessary, but in most cases, AutoPriority should be satisfactory.
  
  
• New option of TCcReplicator allowing to cache the lists of field names of each table from one replication session to another. If TCcReplicator.AutoClearMetadata is set to false, the list of fields is kept in cache from one session to another, else it is cleared at the end of every session. Keeping the metadata in cache can improve performance, particularly in cases where replication is frequent and each replication cycle contains only small amounts of data.
  
  
• New method ClearMetadataCache, allowing to manually clear the metadata cache, which is not done automatically if AutoClearMetadata is false. This is important if a field has been added or dropped, so that the metadata changes can be taken into account.
  
  
• Improved error messages to give more context information
  
  
• Added RPL$LOG.SENT_FROM field, indicating the node in which each change originated.
   
• Added a database upgrader tool for easing upgrades to the new v3 database structure.

Version 3.00.0 (29th of May 2009)

Unreleased internal version

• Added support for MySQL / PHP. That is, replication can occur between any supported database type (Firebird, Interbase, MS SQL) and a MySQL database, through a PHP transport server. This means that by simply adding a few PHP files to your web server, you can allow (authenticated) access to your MySQL database to synchronize data between MySQL and any other supported database type!