Alyx

I don't think it's possible, as wisthy said the effects lava has on entities are managed by the entities (great job there mojang, really) so we can't change the damage...

If your attribute is camelCase, underscored is false, and you end up with the column name for that attribute being PascalCase, that's a bug. What do your models & associations...

You set modelName to `User`, in the documentation modelName is `user`. This is the reason why your generated column was called `UserId` and not `userId`. We can fix the documentation...

`createdAt` and `updatedAt` are not used for anything by sequelize itself. It's safe to disable them, and add your own. `deletedAt` is necessary if the model is [paranoid](https://sequelize.org/docs/v6/core-concepts/paranoid/)

We're resolving these sort of issues in https://github.com/sequelize/sequelize/pull/14280 by introducing the new `inverse` option. Instead of writing ```js Address.belongsTo(User, { targetKey: "id" }); User.hasOne(Address, { sourceKey: "id" }); ``` you'll...

I think we should update the testimonial instead of disabling these

Yep. Re-reading my comment I see how ambiguous it is :)

That will only work when eager loading, but will break all lazy-loaders. I do not recommend doing this. I also don't see what this fixes. Could you provide a query...

There is a warning about it in [the new documentation](https://github.com/sequelize/website/pull/330): https://648dd325deb93b14ad86d83a--sequelize-site.netlify.app/docs/v7/associations/polymorphic-associations/#single-model-single-foreign-key-polymorphic-associations But the proposed solution is unfortunately not something we can put in our documentation, as it will only lead...

Moved to the documentation website as it's where we keep issues related to the documentation. I can already provide some info, the retry option is passed to this library: https://www.npmjs.com/package/retry-as-promised....