Hi Dave,
Will pick this up - https://redmine.postgresql.org/issues/3289
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"
On Fri, May 18, 2018 at 1:25 PM, Dave Page wrote:
> EDB team; I forget which one of
EDB team; I forget which one of you was going to look into the existing
ticket about issues with SQL_ASCII handling, but here's some more
information that may help. Please take a look ASAP.
Thanks.
On Thu, May 17, 2018 at 5:53 PM, richard coleman <
rcoleman.ascen...@gmail.com> wrote:
> Dave,
>
>
Dave,
Thanks for getting back to me on this issue. If this is the case then it
would seem that using python for pgAdmin4 development was a poor choice
considering the fact that PostgreSQL 10 supports more than two dozen types
of encoding, only one of which is UTF8.
In my case I have a SQL_ASCII
On Thu, May 17, 2018 at 3:06 PM, richard coleman <
rcoleman.ascen...@gmail.com> wrote:
> Why is pgAdmin 4 so hostile to SQL_ASCII databases?
>
> We have several production databases dating back to 9.1 that are SQL_ASCII
> encoding but in pgAdmin4 I am constantly having to *clean up* non *UTF8* dat
Why is pgAdmin 4 so hostile to SQL_ASCII databases?
We have several production databases dating back to 9.1 that are SQL_ASCII
encoding but in pgAdmin4 I am constantly having to *clean up* non *UTF8* data.
The same data works just fine in the pgAdmin3 series.
Running the same query in psql yields
