Aris Feryanto a écrit :

Hi,

----- Original Message -----

From: Piotr Przybylski <piotr.prz@gmail.com>

W dniu 18 czerwca 2011 13:31 użytkownik Dieter Adriaenssens

<dieter.adriaenssens@gmail.com> napisał:

2011/6/17 Piotr Przybylski <piotr.prz@gmail.com>:

2011/6/17 Michal Čihař <michal@cihar.com>:

Hi

Dne Fri, 17 Jun 2011 08:10:03 +0700

Aris Feryanto <aris_feryanto@yahoo.com> napsal(a):

Also, I've just checked, some other features, for example

tracking feature, also doesn't honor current server. If user have same db

and table name in different server, tracking will considered both as one db and

table. Is this behavior expected?

As tracking is configured per server, this is clearly a bug.

Silly me. Sorry for wrong report above. I was not clear about this before.

In my test for tracking feature, I used same cloned server in my localhost.

So, there is no bug for tracking.

I wonder how this should be fixed - by storing server id from config

(and risking difficult to detect conflicts when config is changed), or

by stating that tracking and recent tables need to have different

table for each server (and making installation more difficult).

hostname/connection string?

Yes, connection string would work.

I've fixed this in my git (commit 6e65d3d7fc04653be59e133acfe5f10f5eb6cbc5). Marc, could you please merge this in official master branch?

Thanks.

Aris,
I merged commit ede177c577668a712e0d89a8c895c1d0c200f42f because there
seemed to have more recent fixes in your repo. I hope this is fine.