Sequelize.BOOLEAN currently forces user to have to input a value on insert/update about sequelize

[sdepold]

Yep you are right. I've chosen NOT NULL because it doesn't make any sense to have a boolean value with 3 states ^_^ The problem is, that you currently can't set default values. But I really have to implement that. If done, you will be able to just set the default for the boolean values. For now I would recommend to not allow NULL but to set a default :)

[assertchris]

I tried NULL with a default but couldn't get it to work. It created the table with the correct defaults but tried to set the booleans to NULL on insert/update... :/

[sdepold]

hey I just implemented default values and the possibility declare a field as non-null/null field.

please let me know if this works nicely :) I will change the documentation soon, but for now:

s.define("foobar", {
aBoolean: { type: Sequelize.BOOLEAN, allowNull: false, default: false },
aString: Sequelize.STRING
})

this will define the field aBoolean with the default of false and which is not allowed to save a null value

furthermore you will get a field aString which is just the normal varchar string :)

[sdepold]

if that works nicely i will push a new version 0.4 to github/npm

[sdepold]

and the documentation: http://sequelizejs.com/#basicMapping

[assertchris]

Very nice! Will try it out today.

[sdepold]

this seems to work :)