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 comma-separated
list of tables, or maybe tables by mask (regexp?). Of course, both
SQL solutions (database level and table level) may co-exist.
Agreed. However, would be database and table level definitions
independent, or would we translate database level to batch of table
ones? First would allow independent revocation but would complicate
processing.
That's probably one of the most important problems here. Should
replication set given at database level to SAM% tables include SAMPLE7
table created after replication setup? As far as I understand with
current configuration-file based approach such table will be included.
And if we want to keep curretn behavior we can hardly translate DB level
to batch of tables.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
