Open GoogleCodeExporter opened 9 years ago
Original comment by linas.vi...@continuent.com
on 19 Dec 2014 at 6:59
This issue seems to be related to MySQL master host.
In my case, I was testing on MacOS, which does not use case sensitive
identifiers.
This can be solved by adding case sensitive metadata flag to events metadata.
On the slave, if the event is marked as not case sensitive, it is stored or
retrieved from cache use lower case letters.
Otherwise, it is stored in the same case as it was extracted from master.
We should also probably flush the cache if we detect a change in case
sensitivity (in order to be sure that we get correct behavior -- not mixing
table name that were normalized in lower case and table name that are case
sensitive).
Not sure if we want to commit this kind of change now or later.
Original comment by stephane...@continuent.com
on 19 Dec 2014 at 10:59
This can be delayed
Original comment by stephane...@continuent.com
on 15 Jan 2015 at 3:26
Original comment by linas.vi...@continuent.com
on 19 Jan 2015 at 2:18
Original issue reported on code.google.com by
stephane...@continuent.com
on 13 Dec 2014 at 12:07