Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion User privileges replication

Received: by 10.52.29.193 with SMTP id m1mr2380670vdh.4.1338451005575;
        Thu, 31 May 2012 00:56:45 -0700 (PDT)
X-BeenThere: codership-team@googlegroups.com
Received: by 10.52.98.99 with SMTP id eh3ls359153vdb.3.gmail; Thu, 31 May 2012
 00:56:45 -0700 (PDT)
Received: by 10.52.20.51 with SMTP id k19mr32590vde.8.1338451005087;
        Thu, 31 May 2012 00:56:45 -0700 (PDT)
Date: Thu, 31 May 2012 00:56:44 -0700 (PDT)
From: Laurent MINOST <lolo...@gmail.com>
To: codership-team@googlegroups.com
Message-Id: <eb60db58-cf92-4aaf-9535-6432ef15331f@googlegroups.com>
In-Reply-To: <20120529171059.Horde.7n4ANkv4Cn9PxNjzqeXnKmA@webmail.zoner.fi>
References: <62b86c9f-c85c-4f6e-b1d7-550f78e29e37@googlegroups.com>
 <20120529171059.Horde.7n4ANkv4Cn9PxNjzqeXnKmA@webmail.zoner.fi>
Subject: Re: [codership-team] User privileges replication
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1271_24203062.1338451004636"

------=_Part_1271_24203062.1338451004636
Content-Type: multipart/alternative; 
	boundary="----=_Part_1272_33545476.1338451004636"

------=_Part_1272_33545476.1338451004636
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Seppo,

Thanks for your answer.
Yes, I was thinking of such a problem since SET can be use in many=20
different cases.
Could you please post the LP bug entry URL when you create it so we will be=
=20
able to know when the problem will be fixed ?

Thks a lot !

Laurent

Le mardi 29 mai 2012 16:10:59 UTC+2, Seppo Jaakola a =C3=A9crit :
>
> Hi Laurent,=20
>
> SET PASSWORD is indeed not replicated. However, GRANT commands are  =20
> replicated and this is not consistent behavior, so we probably need to  =
=20
> implement SET PASSWORD replication. I will file a LP bug tracker for  =20
> this task.=20
> This is a bit more complicated to deal with, as the SET command can  =20
> have several variables and we are supposed to replicate only PASSWORD  =
=20
> part of the command.=20
>
> -seppo=20
>
> Quoting Laurent MINOST <lolo...@gmail.com>:=20
>
> > Hi,=20
> >=20
> > Is this normal that this query is not propagated/replicated over the=20
> whole=20
> > cluster please :=20
> >=20
> > SET PASSWORD FOR 'root'@'localhost' =3D PASSWORD( '********' )=20
> >=20
> > This change the local node password on which I'm currently connected bu=
t=20
> > does not update the password on the others connected node ?=20
> >=20
> > Thanks.=20
> > Regards,=20
> >=20
> > Laurent=20
> >=20
>
>
>
------=_Part_1272_33545476.1338451004636
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Seppo,<div><br></div><div>Thanks for your answer.<br>Yes, I was thinking=
 of such a problem since SET can be use in many different cases.</div><div>=
Could you please post the LP bug entry URL when you create it so we will be=
 able to know when the problem will be fixed ?<br><br>Thks a lot !<br><br>L=
aurent<br><br>Le mardi 29 mai 2012 16:10:59 UTC+2, Seppo Jaakola a =C3=A9cr=
it&nbsp;:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: =
0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Hi Laurent,
<br>
<br>SET PASSWORD is indeed not replicated. However, GRANT commands are &nbs=
p;
<br>replicated and this is not consistent behavior, so we probably need to =
&nbsp;
<br>implement SET PASSWORD replication. I will file a LP bug tracker for &n=
bsp;
<br>this task.
<br>This is a bit more complicated to deal with, as the SET command can &nb=
sp;
<br>have several variables and we are supposed to replicate only PASSWORD &=
nbsp;
<br>part of the command.
<br>
<br>-seppo
<br>
<br>Quoting Laurent MINOST &lt;<a href=3D"mailto:lolo...@gmail.com" target=
=3D"_blank">lolo...@gmail.com</a>&gt;:
<br>
<br>&gt; Hi,
<br>&gt;
<br>&gt; Is this normal that this query is not propagated/replicated over t=
he whole
<br>&gt; cluster please :
<br>&gt;
<br>&gt; SET PASSWORD FOR 'root'@'localhost' =3D PASSWORD( '********' )
<br>&gt;
<br>&gt; This change the local node password on which I'm currently connect=
ed but
<br>&gt; does not update the password on the others connected node ?
<br>&gt;
<br>&gt; Thanks.
<br>&gt; Regards,
<br>&gt;
<br>&gt; Laurent
<br>&gt;
<br>
<br>
<br></blockquote></div>
------=_Part_1272_33545476.1338451004636--

------=_Part_1271_24203062.1338451004636--