toJSON converting booleans to "t" (true) or "f" (false)

What are you doing?

I have the user model as defined below.

// User model

sequelize.define('user', {
  email: {
    type: STRING,
    allowNull: false,
    unique: true,
    validate: {
      isEmail: true,
      notEmpty: true
    }
  },
  password: {
    type: STRING,
    allowNull: false,
    visible: []
  },
  firstName: {
    type: STRING,
    allowNull: false
  },
  lastName: {
    type: STRING,
    allowNull: false
  },
  active: {
    type: BOOLEAN,
    allowNull: false,
    defaultValue: true
  },
  role: {
    type: STRING,
    allowNull: false,
    defaultValue: 'user'
  },
  isVerified: {
    type: BOOLEAN,
    defaultValue: false
  },
  resetPasswordToken: {
    type: STRING,
    allowNull: true,
    visible: []
  },
  resetPasswordExpires: {
    type: DATE,
    allowNull: true,
    visible: []
  },
  lastLogoutTime: {
    type: DATE,
    allowNull: true,
    visible: ['admin']
  }
});

What do you expect to happen?

toJSON should retain booleans and not convert them to strings

What is actually happening?

When I call toJSON of any instance of User in my CI tests (running in as a docker container with node 8.9.1), all booleans, for example fields active and isVerified, get converted to “t” or “f”.

The problem doesn’t happen when I run it on MacOS 10.12.15 running Node 8.9.1

Output, either JSON or SQL

Dialect: postgres Dialect version: XXX Database version: 9.5 Sequelize version: 4.2.0 Tested with latest release: yes (If yes, specify that version)

Note : Your issue may be ignored OR closed by maintainers if it’s not tested against latest version OR does not follow issue template.

[sushantdhiman]

Thanks @kapvode for a proper test case. As suspected a model with ENUM fetch OIDs properly but wont refresh base types like BOOLEAN in this case.

Everyone please use https://github.com/sequelize/sequelize/pull/8851 patch and verify if that fix this issue. After verification and review from other maintainers I will merge that PR.

[karn09]

I’m seeing this same issue, but with 4.26.0. @jonahlau Did you mean 4.26.0 as well? You had marked yes to tested with latest.

Downgrading to 4.25.2 fixed the issue for me.