Null constraint error while Default value is set Ruby On Rails - Postgresql

Question

In my database i have a table with schema like below

  create_table "external_source", force: :cascade do |t|
    t.string   "external_id"
    t.string   "permalink",                             null: false
    t.datetime "created_at",                            null: false
    t.datetime "updated_at",                            null: false
    t.boolean  "is_deleted",         default: false,    null: false
    t.string   "company_name",       default: ""
    t.boolean  "hide_salary",        default: true,     null: false
  end

But when i tried to insert values without is_deleted parameter, Rails server throws null constraint violation error like:

ActiveRecord::StatementInvalid (PG::NotNullViolation: ERROR: null value in column "is_deleted" violates not-null constraint

Now when I have set its default value I am not expecting this error. can you tell me what wrong am I doing. Thank You

here is the JSON to insert

{
  "data":
  [
    {
      "external_id":"2262a0228sf-1b9e-sd4e76-b5d7-a8ba01783ebb9i3413139",
      "permalink": '234242341',
      "hide": true,
      "company_name": "com1",
    }
  ]
}

Please post the code that does the create statement.

Anton
– Anton

2018-07-14 12:56:01 +00:00
Commented Jul 14, 2018 at 12:56 — Anton
– Anton, Commented Jul 14, 2018 at 12:56
@Anton i updated with json

Mani
– Mani

2018-07-14 13:08:03 +00:00
Commented Jul 14, 2018 at 13:08 — Mani
– Mani, Commented Jul 14, 2018 at 13:08
Great! Please add the controller code as well.

Anton
– Anton

2018-07-14 13:13:32 +00:00
Commented Jul 14, 2018 at 13:13 — Anton
– Anton, Commented Jul 14, 2018 at 13:13

Shabini Rajadas · Accepted Answer · 2018-07-14 14:32:31Z

2

null and default have different purposes in the migration. If you want the default value to be set as false, when no value is set in the controller just use,

default: false,

there is no need to use the null:false parameter in your case. default would do the work for you. For more explanation of null and default please check the following link How do :default => 0 and :null => false differ for integer fields in migrations?

answered Jul 14, 2018 at 14:32

Shabini Rajadas

7718 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Mani Over a year ago

i was doing this thing before which didn't worked so i added null: false which also didn't work

Shabini Rajadas Over a year ago

Can you please add the controller code used for creation.

Shabini Rajadas Over a year ago

What does ExternalSource.new display in rails console?

Mani Over a year ago

sorry for late reply. internet is really bad. yeah that shows the default values. i check.

Shabini Rajadas Over a year ago

Then there is something wrong with the controller code. Remove the null: false from the migration file and check the code in controller.

|

MaciekR · Accepted Answer · 2018-07-16 13:56:09Z

0

Maybe there is a validation in model, sth like validates :is_deleted, presence: true? if so:

get rid of this validation, or
keep validation and set as false by default (if missing), i.e.
```
def default_deleted_status
  self.status ||= false
end
```

answered Jul 16, 2018 at 13:56

MaciekR

3024 silver badges19 bronze badges

Collectives™ on Stack Overflow

Null constraint error while Default value is set Ruby On Rails - Postgresql

2 Answers 2

6 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related