Re: [pgAdmin4][Patch]: RM #3077 - ERROR: invalid byte sequence forencoding "LATIN1":0x00

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: [pgAdmin4][Patch]: RM #3077 - ERROR: invalid byte sequence forencoding "LATIN1":0x00
Дата
Msg-id CA+OCxowewcNdbkyHe-1Y0w3HA3R_eTKA5mBKDvF48PArj4pp0Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [pgAdmin4][Patch]: RM #3077 - ERROR: invalid byte sequence forencoding "LATIN1":0x00  (Joao De Almeida Pereira <jdealmeidapereira@pivotal.io>)
Ответы Re: [pgAdmin4][Patch]: RM #3077 - ERROR: invalid byte sequence forencoding "LATIN1":0x00
Список pgadmin-hackers
Дерево обсуждения


On Wed, Feb 21, 2018 at 3:45 PM, Joao De Almeida Pereira <jdealmeidapereira@pivotal.io> wrote:
Hi 
The patch looks good, do we have any example error that we can test in order to ensure the problem no longer shows up in the future?
If they could be Unit Tests instead of Feature tests that would be awesome, because Feature tests are much more expensive then Unit.

I think we need to consider a couple of options here:

1) Make sure that many/all of our tests use non-ASCII names.

2) Consider adding a mechanism to allow running the regression tests with overridden GUC values. For example, a parameter in the test config file that gives a set of GUCs to change upon connection.

The downside of 2 of course, is that it adds a huge amount of possible environment combinations to test.

Thoughts?
 
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

В списке pgadmin-hackers по дате отправления: