Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Pavel Cisar
Hi, Dne 21. 02. 19 v 11:15 Dimitry Sibiryakov napsal(a): 21.02.2019 10:46, Pavel Cisar wrote: It's tempting, but I see potential for problems. If we would allow multiple sets & filters at master node, there is no need to have them at replica. And if replica would have different definitions tha

Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Dmitry Yemanov
21.02.2019 12:46, Pavel Cisar wrote: And one partially related question from another angle: does it make sense to implement also replica-side declarative filtering? I mean the case where changes for all tables are journaled but for some reason only some tables should be applied to replica - e

Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Dimitry Sibiryakov
21.02.2019 10:46, Pavel Cisar wrote: It's tempting, but I see potential for problems. If we would allow multiple sets & filters at master node, there is no need to have them at replica. And if replica would have different definitions than master, then it's not possible to replace master with rep

Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Dimitry Sibiryakov
21.02.2019 9:14, Dmitry Yemanov wrote: Second, IMHO declaring tables as "publishable" via CREATE|ALTER TABLE is too restrictive. I'd rather manage the replication set using some global commands, be it ALTER DATABASE or something different, allowing to include/exclude all tables at once, or comma

Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Alex Peshkoff via Firebird-devel
On 2/21/19 12:46 PM, Pavel Cisar wrote: Second, IMHO declaring tables as "publishable" via CREATE|ALTER TABLE is too restrictive. I'd rather manage the replication set using some global commands, be it ALTER DATABASE or something different, allowing to include/exclude all tables at once, or co

Re: [Firebird-devel] Replication: declarative control

2019-02-21 Thread Pavel Cisar
Hi, Generally, I like the DDL approach more than using the configuration file. Additional benefit to ones listed is possibility to create various front-ends for replication configuration / integration of such functionality into existing Firebird management tools. Comments to specific questio

[Firebird-devel] Replication: declarative control

2019-02-21 Thread Dmitry Yemanov
All, In v4 Beta, replication is fully driven by the configuration file. In particular, tables to be replicated are (optionally) defined using two regexp-based options: include_filter and exclude_filter. This was the easiest solution that doesn't require ODS changes and this matches the trace/