Add default option to #attribute in collection about model HOT 5 CLOSED

I was researching this issue with the example proposed by @jodosha in #134

I was trying to set the default value if the value from database is nil and default isn't nil in https://github.com/lotus/model/blob/master/lib/lotus/model/mapping/coercer.rb#L69 but the "compilation" with this issue turn me on crazy.

an example:

in the from_record method, record is a hash

{id: 1, name: 'Luca', admin: nil}

and then a Hash is constructed in the line before commented, with the values coerced and used to build a new entity.

Do you think it's useful something like this?

from model.

There's a bigger problem here: imagine that the admin column in the example above is non-NULLable in addition to having a default set. Currently, if you don't explicitly set the value in the entity then Lotus sends column => nil on serialisation. This causes Postgres, at least, to choke and error - you can't explicitly set a non-nullable value to null.

It also suggests that we're explicitly setting columns with default values to null when we might expect them to use the column default

from model.

@jodosha @AlfonsoUceda

$ LOTUS_ENV=test bundle exec lotus db prepare
Unsupported ruby class used as database type: Boolean (Sequel::Error)

How did you define the Sequel's TrueClass FalseClass?

from model.

@theCrab We use Sequel as migration engine. The list of Ruby types is defined here: http://lotusrb.org/guides/migrations/create-table/ 😸

from model.

Closing this for now, as we want to narrow the scope as much as possible before to hit 1.0.

from model.