jsonb properties are included in the returned AR models even though they are not selected

[breis-sa]

Hello! I'm using the latest version of the gem (1.4.0) and noticed a slightly odd behavior:

Say I have the following table

# config/schema.rb

create_table "examples", force: :cascade do |t|
  t.string "name"
  t.jsonb "configuration"
end

and model

# app/models/product.rb

class Example< ApplicationRecord
  jsonb_accessor :configuration,
                   foo: [:boolean, { default: false }],
                   bar: [:boolean, { default: false }],
                   baz: [:boolean, { default: false }]
end

if then I do

Example.select("id, name").first.attributes

I get

=> {"id"=>1, "name"=>"Example One", "foo"=>false, "bar"=>false, "baz"=>false}

Even though I did not include the configuration column or any of its properties in the select clause. Is that expected?

[ashkulz]

@breis-sa I don't think this is expected; I'm guessing this is happening of the after_initialize hook setting the default values. Unfortunately, I'm not sure if this can be avoided -- how do you distinguish between using select with limited columns and a new instance being created in the context of that?