From: | "Gavan Schneider" <list(dot)pg(dot)gavan(at)pendari(dot)org> |
---|---|
To: | "Sachin Kumar" <sachinkumaras(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org, krishna(at)thewebconz(dot)com |
Subject: | Re: How to manage null value while copy data from csv |
Date: | 2020-12-31 07:59:33 |
Message-ID: | 95624F2E-5D82-4B3B-BC0A-B20F3DCC5150@pendari.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 31 Dec 2020, at 17:25, Sachin Kumar wrote:
> when I am uploading data (CSV File) using the COPY command. I am
> getting
> below mention error.
>
> ERROR: null value in column "adj_type" violates not-null constraint.
>
This indicates the relevant column in the database table has been
defined to **never** allow a NULL value.
> When I define null it gives no error message, but how to manage null
> value
> n data without defining it, because there is many more columns. when
> it
> defines null it gives an error if null value comes you are violating
> null.
>
What is meant by “define null”? Is this where you put a real value
in the CSV, or a dummy text value such as “null”?
You could massage the csv so all the gaps get a dummy value, then handle
this in the SQL table.
Otherwise
> Please suggest how to manage null value in postgresql?
>
Basic options
1. Fix the raw csv data so there are no gaps — the person who defined
the database wasn’t expecting any
2. Fix the database so it will accept NULL values — assuming this is
ok with the business model
3. Accept the csv data into a temporary table which tolerates NULL,
massage the data then insert into the real database
Regards
Gavan Schneider
From | Date | Subject | |
---|---|---|---|
Next Message | MichaelDBA | 2020-12-31 17:30:49 | Re: Creating a materialized view causing blocks |
Previous Message | Sachin Kumar | 2020-12-31 06:25:39 | How to manage null value while copy data from csv |