Alyx

Definitely need to check first, but that would be nice as well

We're finally working on this The high level plan is to have individual packages for each dialect, such as `@sequelize/postgres`, `@sequelize/mariadb`, `@sequelize/oracle`, etc Each package will provide all the dialect-specific...

@WikiRik for the task about updating the documentation, note that we now have this project to keep track of which PRs still need to be documented: https://github.com/orgs/sequelize/projects/5

If we're going to add support for better-sqlite3, maybe we should rename the `@sequelize/sqlite` to `@sequelize/sqlite3` to reflect the name of the library that is used by it. We'd then...

Note that there will eventually be a global option to configure the defaults, but the exact API is still TBD, so even if we pick replacements by default, you could...

The problem with `@sequelize/sqlite/better-sqlite` is that it requires installing both dialect libraries. If we want to deduplicate code between the two, we can just publish `@sequelize/abstract-sqlite` that is not connector-dependant...

To be consistent, we probably should. Considering the demand has only ever been for sqlite, that may not be worth the trouble.

Following the changes done in https://github.com/sequelize/sequelize/pull/17222, it will be very important to have a clear page that explains how to configure the credentials per dialect. Right now it's in the...

Considering DB2 is really DB2 for Linux, Unix, Windows, and ibmi is really DB2 for IBM i, should we rename the packages to `@sequelize/db2-luw` and `@sequelize/db2-ibmi` respectively? Following discussion with...

PR https://github.com/sequelize/sequelize/pull/17222 normalizes everything related to connection options. The values at the root of the option bag are now only used as the default values of the write and read...