On 29 Jul 2005 at 8:04, elleffeci wrote:

>No. SQL parser in FB1.5 is more strictive.
>
>Oh, gosh: do you mean we could get some parse errors?!

As you was already told, you could get errors on SQL queries that
used to work on FB1.

>That could be very good: I sketched the index of 'The Firebird Book'
>but I did not find the term 'replication'.

No wonder. If Helen had to describe all tools which could be used
with FB (and DBMS in common), her book would be non-liftable.

>Any pointer to sources that
>can explain what you mean by replication and how to perform it will be
>greatly appreciated, Dmitry!

Google is your friend. Here is some quotes from IBPReplicator docs
(http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_replicator).

> What is IBReplicator?
>
>IBReplicator is an additional software management system that allows
>users to synchronise, create and maintain identical copies of
>databases and database tables from source databases to target
>databases on multiple local and remote sites.

> Benefits of IBReplicator
>
>Replication can improve:
>
>Data availability - Work groups can have their own copy of a
>replicated database, and can therefore function independently on a
>larger network. A local copy of a database means that the work group
>does not have to compete for larger network resources accessing
>databases on other remote sites. Decision support applications can
>be separated from high throughput transactional applications if
>necessary, which can also reduce network traffic and can improve
>data availability and system performance.
>
>Data reliability - Replicated databases can be maintained for
>improved system fault tolerance. Applications can switch from
>original source databases to replicated copies in the event of
>system failure.
>
>Data flexibility - Every organisation typically has its own
>replication requirements and could be operating over a wide variety
>of databases. IBReplicator allows you to replicate full databases, a
>subset of tables, selected rows and columns from a source database
>to a number of target databases. You can specify when you want
>replication to occur; on a predefined per second schedule (virtually
>continuously), on a time based schedule (hourly, daily, weekly), or
>when a specific event occurs, or whether you want replication to
>take place manually. You can define multiple replication schemas
>that will allow you to replicate (if required) different source
>database subsets to multiple targets.

--
SY, Dimitry Sibiryakov.