Alyx
Alyx
@tapiwakundi Sure! Feel free to give it a try
Sequelize 7's datatypes are strict mode compliant so all we're missing is an sqlite-specific "strict" option
As the person that wrote that, I am honestly unsure. This may be a bug
Could be fixed easily by always adding `NULL` is `allowNull` is true or undefined here https://github.com/sequelize/sequelize/blob/491ff159cda4aab72bad558fce533fc98e09ae7f/src/dialects/mysql/query-generator.js#L373
It should be! But we should also add an integration test to ensure NULL can be inserted in a nullable TIMESTAMP table with mariadb
That sounds reasonable to me. In methods that generate bind parameters (update, insert), the `where` object should be built using bind parameters too instead of replacements. If we go down...
Sequelize resets the 'changed' state of its attributes after the query has completed (https://github.com/sequelize/sequelize/blob/main/src/model.js#L4165). We could create a copy of `dataValues` at the start of the query then only reset...
Yep, looks like it should be `fireOnArray: Array` instead (or is it lowercase?)
Not currently, but we'd be open to a PR that implements this. In the meantime, you can customize the `ON` clause (noticed that after responding on slack): ``` User.findAll({ include:...
Still the same status, nobody from the core team is currently working on this. Someone from the community taking the lead on this is the current best chance to get...