Dirty problems using Sequel and Mobility

[shioyama]

Dirty problems using Sequel and Mobility

[shioyama]

The fix for this issue has been released in version 0.2.2.

[shioyama]

Does this happen if you use Mobility version 0.1.20 ?

[jnylen]

Nope, it returns the same for 0.1.20.

[shioyama]

I can reproduce this. It seems to be a problem with the jsonb columns not having a default value. In AR this is handled by setting default: '' (in Rails 4 it was default: '{}'), which in the tests happens here. In the case of Sequel this doesn't seem to be happening and I can't find much documentation on it.

Without a default value, this will happen when dirty tries to check the previous value of a new column.

[shioyama]

Hmm... maybe this: jeremyevans/sequel#1330

I'll have to look into this a bit.

[shioyama]

Ok, I confirmed I can fix this with:

plugin :defaults_setter
attributes.each { |attribute| self.default_values[attribute.to_sym] = lambda { ::Sequel.pg_jsonb({}) } }

in the setup block for the jsonb backend. I suppose hstore may need it as well.

[shioyama]

Try the sequel_jsonb_dirty branch, here: https://github.com/shioyama/mobility/tree/sequel_jsonb_dirty

[jnylen]

@shioyama Seems to work.

Thanks again for this gem! :)

[shioyama]

Great, I'll just have a closer look and merge that change in the next couple days. For now pls just use that branch.