Alyx comments

Results 453 comments of


                                            Alyx

BelongsToMany stops working after closing a connection and redefining with a new Sequelize instance: ConnectionManager.getConnection() was called after the connection manager was closed

Starting with [v7.0.0-alpha.38](https://github.com/sequelize/sequelize/releases/tag/v7.0.0-alpha.38) (PR https://github.com/sequelize/sequelize/pull/17077), sequelize models can be registered against another instance after `sequelize.removeAllModels()` has been called I'll keep this open as a reminder to internally call `removeAllModels` when...

SQL parser issue for a specific combination of replacements, "?" symbol matching problem.

Here is a thread about a previous conversation related to this issue: https://github.com/sequelize/sequelize/discussions/15410

SQL parser issue for a specific combination of replacements, "?" symbol matching problem.

The other one is a discussion that was never turned into a bug report so I'm keeping yours open so we don't lose track of it again :)

feat: temporal tables

This is a big PR. Thank you for all the work you've been putting in this ORM I'll need some time to read up & experiment with temporal tables before...

sequelize.sync() does not create schemas

Sure!

Increment or Decrement value using Sequelize upsert() does not work in postgre

That PR landed in Sequelize 7, but you're on Sequelize 6. I'm not aware of this feature being available in Sequelize 6

`Model.destroyMany` to destroy many instances in one query

This aligns nicely with `bulkUpdate`, `bulkSave`, and `bulkUpsert` that we're considering in https://github.com/sequelize/sequelize/issues/4501

`Model.destroyMany` to destroy many instances in one query

We should consider renaming `Model.destroy` -> `Model.bulkDestroy` (because that's what the hook is already called) and calling this method `Model.destroyMany` instead. Same remark for `bulkUpdate`, `bulkSave`, and `bulkUpsert`

Inconsistent and buggy default value parsing by `queryInterface#describeTable`

I'm very late to the party but yeah `describeTable` has many issues and has been blocking me for a long time too. Unfortunately it's rarely a priority given how much...

Inconsistent and buggy default value parsing by `queryInterface#describeTable`

I'd propose to split "default value" into "rawDefaultValue", which contains the unparsed SQL and is always present, and "parsedDefaultValue", which contains the parsed version and can be undefined, as the...