Mike G. wrote:
> Hi,
>
> I read the faq about the problem where pgadmin won't display data if
> it cannot convert the data due to an encoding issue.
>
> I have a table created under Latin1. When doing a select * from that
> table and exporting the results to a file pgadmin was dropping a row
> without warning. That row was being displayed within a pgadmin
> window and one of the columns did have data in it that appeared to
> not be converting correctly.
>
> By selecting the export encoding method of utf-8 and then exporting
> the result that row would appear in the file. If no default method
> was selected or the local charset selected (probably utf-16 since
> this is on WinXP) the row would not be exported to the file.
>
> Shouldn't pgadmin generate a warning that all rows were not exported
> or abort the export process instead of silently removing the row?
I agree, pgAdmin shouldn't write garbage silently. Can you provide an
example?
Regards,
Andreas