pgadmin-org / pgadmin-org/pgadmin4
Add a UTF BOM to the CSV produced by "Save Results to File" where appropriate
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Describe the solution you'd like
When a database uses a UTF-8/16/32 encoding add the appropriate Byte Order Mark to the file produced by "Save Results To File"
Describe alternatives you've considered
- Tell every Excel loving data-scientist to always use the "Get Data From Text" wizard and select the right character encoding manually.
- Allow a per-client encoding configuration and use on-the-fly character set conversion to always export data in the configured encoding.
Additional context
Many windows applications assume the encoding is ANSI or ASCII unless a BOM is present.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation behind the “Save Results To File” action and how it determines the database encoding. Trace the CSV export path and identify the existing tests for exported files, then verify that the appropriate BOM is present for UTF-8, UTF-16, and UTF-32 databases without changing other encodings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100