[pgimport] Option to do not store values as NULL

Open
#362 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
postgresql, python
Domain
cli, databases

Research direction

Start by locating the pgimport function and its CLI equivalent, then trace how NULL values are currently written. Define the option's behavior so selected empty values are stored as empty strings instead of NULL, and verify both entry points handle it consistently.

Written by the indexing model from the issue text.

Description

cli enhancement plugin utils

NULL values can be confusing when analyzing data and there will be some cases where we prefer to add empty values as empty strings instead of NULL. The function pgimport (and the CLI equivalent) should have an option to deal with this scenario.

Dominant language
Python
Stars
886
Forks
137
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from turicas/rows

All issues in turicas/rows

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.