that you need is this one:
> https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/Filters/Regex-Filter.md
>
> Hope that this helps.
>
> Federico
>
>
>
> Mar 22/12/15, Michele Tota ha scritto:
>
> Og
b.com/mariadb-corporation/MaxScale/blob/master/Documentation/Filters/Regex-Filter.md
Hope that this helps.
Federico
Mar 22/12/15, Michele Tota ha scritto:
Oggetto: Re: [Maria-discuss] enforce_storage_engine galera cluster
A: maria-di
eds to be manually enabled on all nodes)
Federico
Mar 22/12/15, Michele Tota mailto:michele.t...@lnf.infn.it>> ha scritto:
Oggetto: Re: [Maria-discuss] enforce_storage_engine galera cluster
A: maria-discuss@lists.launchpad.net
sort of support for MyISAM, but it's unreliable and
> needs to be manually enabled on all nodes)
>
> Federico
>
>
>
> Mar 22/12/15, Michele Tota ha scritto:
>
> Oggetto: Re: [Maria-discuss] enforce_storage_engine galera clus
odes)
Federico
Mar 22/12/15, Michele Tota ha scritto:
Oggetto: Re: [Maria-discuss] enforce_storage_engine galera cluster
A: maria-discuss@lists.launchpad.net
Data: Martedì 22 dicembre 2015, 12:22
Thanks guys,
as Ian has pointed out, in recent releases sql
Thanks guys,
as Ian has pointed out, in recent releases sql_mode contains by default
NO_ENGINE_SUBSTITUTION so in our deployment we set sql_mode to blank to
gracefully use InnoDB when MyISAM table creation is issued.
To be clearer on the problem we're experiencing, I'll paste some console
outpu
On 21/12/2015 20:10, Nirbhay Choubey wrote:
>
> On Mon, Dec 21, 2015 at 12:47 PM, Michele Tota
> mailto:michele.t...@lnf.infn.it>> wrote:
>
> Hello Nirbhay,
> thanks for your reply. We have the 10.1.9 mariadb version; the bug
> that your refers is similar but in our case the enforcing w
On Mon, Dec 21, 2015 at 12:47 PM, Michele Tota
wrote:
> Hello Nirbhay,
> thanks for your reply. We have the 10.1.9 mariadb version; the bug that
> your refers is similar but in our case the enforcing works properly on the
> node used for the initial write, while replicated writes on other nodes
>
Hello Nirbhay,
thanks for your reply. We have the 10.1.9 mariadb version; the bug that
your refers is similar but in our case the enforcing works properly on
the node used for the initial write, while replicated writes on other
nodes generate tables using another engine.
On 21/12/2015 18:41,
Hi!
On Mon, Dec 21, 2015 at 12:23 PM, Michele Tota
wrote:
> Hi,
> we have a problem using enforce_storage_engine variable set to InnoDB.
> We have three servers in cluster (multi masters).
> When we issue create table with engine=MyISAM the engine is correctly
> enforced to InnoDB only on the no
Hi,
we have a problem using enforce_storage_engine variable set to InnoDB.
We have three servers in cluster (multi masters).
When we issue create table with engine=MyISAM the engine is correctly
enforced to InnoDB only on the node we are connected to. On the other
nodes the replicated table is c
Hi
What is the reason for the the new enforce_storage_engine option being
session only? Percona's implementation is global, and I realise there
was a request to make it less strict, and be overridden by session for
users with the super privilege, but surely it would make sense to allow
a glob
12 matches
Mail list logo
