From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgAdmin4 v 5.3 export error |
Date: | 2021-06-08 05:01:28 |
Message-ID: | CAFOhELczn4Oa7+5wNin=FK0GnLmOLh9zSEqeLQcBRPe+tHVY0Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
This issue has already been reported and it will be fixed soon.
Ref: https://redmine.postgresql.org/issues/6507
Thanks,
Khushboo
On Tue, Jun 8, 2021 at 1:38 AM richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>
wrote:
> To whom it may concern,
>
> I think I've come across a *nasty* bug in the text exporter. When the
> table contains character varying field that contain numbers, the text
> exporter is now appending *.0* to the end of cell data that contains
> numeric values. It has also started removing any leading zeros. These
> zeros are significant (which is why the field they exist in are character
> varying).
>
> These two bugs render the text export option useless for this type of data.
>
> Screenshot of the data as shown in pgAdmin4 (note the *pro* and *xref*
> fields):
> [image: pg4_bug_tableOutput.png]
>
> Here is the screenshot of the data that pgAdmin4 *now* generates (note
> the *pro* and *xref* fields):
> [image: pg4_bug_textOutput.png]
>
> If someone could look into this that would be appreciated.
>
> thanks.
>
> version 5.3
> Python Version 3.8.8
> Flask Version 1.1.4
> Application Mode: Desktop
> OS: Windows 10 Enterprise x64
>
From | Date | Subject | |
---|---|---|---|
Next Message | richard coleman | 2021-06-08 05:08:42 | Re: pgAdmin4 v 5.3 export error |
Previous Message | richard coleman | 2021-06-07 20:07:52 | pgAdmin4 v 5.3 export error |