It's why adding configuration parameter in pgadmin for file extension could
solve the problem for most of people.
And encoding in same Time would be complete...
Le sam. 6 févr. 2021 à 00:17, Dave Caughey a écrit :
>
> On Fri, Feb 5, 2021 at 3:39 PM richard coleman <
> rcoleman.ascen...@gmail.com
On Fri, Feb 5, 2021 at 3:39 PM richard coleman
wrote:
> Dave,
>
> I concur with Alain.
>
> On Fri, Feb 5, 2021 at 3:22 PM Dave Caughey wrote:
>
>> Always naming the file as ".csv", regardless of the delimited used, was a
>> bug that was fixed.
>>
>> In my case it was a bug that was created.
>
>
All,
Sorry for inserting my opinion here, but I am sick of programs that make
apologies for the fact the Microsoft Office is broken. Outlook can’t display
HTML, so people have to jump through hoops, to turn HTML into Vector Markup
Language (VML). Excel assumes all files ending in ‘csv’ are co
Dave,
I concur with Alain.
On Fri, Feb 5, 2021 at 3:22 PM Dave Caughey wrote:
> Always naming the file as ".csv", regardless of the delimited used, was a
> bug that was fixed.
>
> In my case it was a bug that was created.
> The problem with always naming a file as ".csv" is that Excel then bl
Always naming the file as ".csv", regardless of the delimited used, was a
bug that was fixed.
The problem with always naming a file as ".csv" is that Excel then blindly
assumes that the file actually does contain comma-delimited fields, and
bypasses the Import From Text Wizard, so if you use anyth
Hi,
I'm using frequently the download file function in the query tool. In previous
version of PgAdmin4, I select field separator ";" and file was always
generated with extension .csv and can be opened directly by Excel in one click
with correct columns !
Now I have always .txt extension (since
