Enhance pgimport/pgexport
Open
Nobody has claimed this yet.
cli
enhancement
- Dominant language
- Python
- Stars
- 886
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
Tasks:
- (pgimport) Fix
--no-create-tableso we don't need to pass=true - (pgimport) Fix error when quotechar is detected as
'(the escape does not work) - (pgexport) Be able to specify a query instead of table name, so we can export more complex data (this could be used to optimize
rows query) - (pgimport and pgexport) Be able to specify field names, like
--fields - (pgimport and pgexport) Be able to force the CSV dialect
- (pgimport and pgexport) Create docs
- (pgimport) If the table does not exist and we pass
--no-create-tablean error will not be raised. Decide if rows should raise an error and how PostgreSQL creates the table (field types) - Update sequences (more info, possible solution)
- Check chunk size for some files (taking too long to detect dialect). Also, print "detecting CSV dialect" while it does not start)
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 reviewing the pgimport and pgexport entry points and the remaining unchecked tasks in this issue, including the PostgreSQL sequence references. Break down the CSV dialect, field-name, table-creation, sequence, and chunk-size work separately; done means each selected behavior is implemented and verified for both commands where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- cli, data, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100