V7-alpha connectionManager.initPools missing

Open
#726 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, postgresql
Domain
backend, databases

Research direction

Start by comparing the Sequelize v6 connectionManager.initPools behavior with the v7-alpha pool lifecycle in @sequelize/core, using the AWS Lambda use case described in the issue. Determine whether v7 provides an equivalent public entry point, then validate the behavior against PostgreSQL and the reported Sequelize v7.0.0-alpha.32 environment.

Written by the indexing model from the issue text.

Description

Issue Creation Checklist

  • I understand that my issue will be automatically closed if I don't fill in the requested information
  • I have read the contribution guidelines

Bug Description

Using V7-alpha the connectionManager no longer has a initPools method to restart the connection pool when using it in an AWS Lambda environment.

Is the way to do this changed in V7? I tried looking through the source but could not find a way to do this with the same behaviour as on V6

Reproducible Example

Here is the link to the SSCCE for this issue:

What do you expect to happen?
What is actually happening?
Environment
  • Sequelize version: 7.0.0-alpha.32
  • Node.js version: v18.16.0
  • If TypeScript related: TypeScript version:
  • Database & Version: PostgreSQL
  • Connector library & Version:

Would you be willing to resolve this issue by submitting a Pull Request?

  • Yes, I have the time and I know how to start.
  • Yes, I have the time but I will need guidance.
  • No, I don't have the time, but my company or I are supporting Sequelize through donations on OpenCollective.
  • No, I don't have the time, and I understand that I will need to wait until someone from the community or maintainers is interested in resolving my issue.

Indicate your interest in the resolution of this issue by adding the 👍 reaction. Comments such as "+1" will be removed.

Dominant language
HTML
Stars
30
Forks
170
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/website

All issues in sequelize/website

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.