Migration with SQLite failed

[UweWagner403]

Based on the example model Article, the expanded model look like this:

class Article < Marten::Model
with_timestamp_fields
field :id, :big_int, primary_key: true, auto: true
field :title, :string, max_size: 255
field :content, :text
field :quelle, :string, max_size: 255, blank: true, default: nil
field :created_at, :date_time, auto_now_add: true, blank: true
field :updated_at, :date_time, auto_now: true, blank: true
end

marten genmigrations generate:
def plan
change_column :main_article, :quelle, :string, max_size: 255
end

I noticed the constraints blank: true and default: nil are not noticed.

marten migrate gives an error: "Unhandled exception: NOT NULL constraint failed: new_main_article.quelle (SQLite3::Exception)".

[ellmetha]

Hey! 👋

I am guessing that this is the field you added to your model?

 field :quelle, :string, max_size: 255, blank: true, default: nil

The blank option doesn't impact migrations because it doesn't impact the definition of columns at the SQL level. If you want your column to be nullable, then you have to specify the null: true option in your model field:

class Article < Marten::Model
  with_timestamp_fields
  field :id, :big_int, primary_key: true, auto: true
  field :title, :string, max_size: 255
  field :content, : text
  field :quelle, :string, max_size: 255, blank: true, null: true, default: nil
  field :created_at, :date_time, auto_now_add: true, blank: true
  field :updated_at, :date_time, auto_now: true, blank: true
end

Please remember that blank: true only affects the validation of your model records: if you only set blank: true in a field without setting null: true, then the corresponding column will require non-null values!

[UweWagner403]

Thanks for the quick reply!