For me configuration error should prevent with working with database at 
all.Consider two entries with same alias but different path this is critical 
configuration error and silently ignore it is not good.Regards,Karol 
Bieniaszewski
-------- Oryginalna wiadomość --------Od: Mark Rotteveel <m...@lawinegevaar.nl> 
Data: 17.05.2021  12:49  (GMT+01:00) Do: firebird-devel@lists.sourceforge.net 
Temat: Re: [Firebird-devel] 4.0 replication - One primary database with
  two modes On 17-05-2021 11:33, Dmitry Yemanov wrote:> Yes, the first wins. 
I'm wondering, however, wouldn't it be better to > raise an error for multiple 
configurations detected for the current > database? Or maybe just log a warning 
and keep using the first entry.I'm on the fence, it's a configuration error 
that might break certain expectations, so it should probably be really "in your 
face" to avoid questions like this.On the other hand, such an error could hurt 
database availability in a production environment by - for example - a 
copy/paste config error, in which case a warning in the log is more 'friendly', 
but might go unnoticed.Mark-- Mark RotteveelFirebird-Devel mailing list, web 
interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to