-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/14 18:05, Mike Bayer wrote:
On Oct 7, 2014, at 8:29 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
That said, I wonder how we're going to manage cases when those
*global* settings for the whole server should be really limited
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 19:10, Mike Bayer wrote:
On Oct 6, 2014, at 9:56 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
But we can do better. We should also enforce utf8 on client
side, so that there is no way to run with a different encoding,
and
On Oct 7, 2014, at 8:29 AM, Ihar Hrachyshka ihrac...@redhat.com wrote:
That said, I wonder how we're going to manage cases when those
*global* settings for the whole server should be really limited to
specific databases. Isn't it better to enforce utf8 on service side,
since we already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
tl;dr we should enforce utf8 on server and client sides of db
connection, and this requires changes to docs and oslo.db. The latter
may require raising effective libpq version dep to 9.1+.
Recently I was working on making sure we always
On 10/06/2014 08:30 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
tl;dr we should enforce utf8 on server and client sides of db
connection, and this requires changes to docs and oslo.db. The latter
may require raising effective libpq version dep to 9.1+.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 15:11, Jay Pipes wrote:
On 10/06/2014 08:30 AM, Ihar Hrachyshka wrote: Hi all,
tl;dr we should enforce utf8 on server and client sides of db
connection, and this requires changes to docs and oslo.db. The
latter may require raising
On Oct 6, 2014, at 9:56 AM, Ihar Hrachyshka ihrac...@redhat.com wrote:
But we can do better. We should also enforce utf8 on client side,
so that there is no way to run with a different encoding, and so
that we may get rid of additional options in sql connection
strings. I've sent a
On Mon, Oct 06, 2014, Ihar Hrachyshka ihrac...@redhat.com wrote:
Maybe it is indeed wasteful, I don't have numbers; though the fact is
we don't allow any migrations for databases with any non utf8 tables
as of [1]. The code was copied in multiple projects (Nova, Glance
among other things).
