As stated during
TSQLRecord fields definition, the ORM is able to maintain a revision
number for any
TSQLRecord table, so that it the table may be
easily synchronized remotely by another
If you define a
TRecordVersion published property, the ORM core
will fill this field just before any write with a monotonically increasing
revision number, and will take care of any deletion, so that those
modifications may be replayed later on any other database.
This synchronization will work as a strict master/slave replication
scheme, as a one-way on demand refresh of a replicated table.
Each write operation on the master database on a given table may be easily reflected on one or several slave databases, with almost no speed nor storage size penalty.