sequelize/sequelize-pool

Issues

• Update connection host. impact on connection pool?

  #56 opened 7 months ago by chaoyangnz
  2

• Custom keepalive on idle connections protected due to minimum pool size

  #55 opened 7 months ago by brandonw
  4

• Moving sequelize-pool inside sequelize monorepo

  #54 opened 9 months ago by WikiRik
  2

• Destroying inactive resources can cause unhandled promise rejection

  #53 opened 10 months ago by sfc-gh-ljagielski
  1

• Min Pool is not respected

  #22 opened 5 years ago by SergeyCherman
  16

• Acquire timeout not respected (seen on MSSQL)

  #52 opened 2 years ago by chrisskalog
  1

• maxUses based on time instead of uses

  #51 opened 2 years ago by intellix
  1

• Not respecting 0 as idle timout as suggested by AWS lambda doc

  #48 opened 2 years ago by mokkabonna
  2

• Question - Monitoring connection pool

  #47 opened 3 years ago by thpoiani
  0

• findAll promise warning

  #13 opened 5 years ago by bohrshaw
  4

• Connection do not close after call sequelize.close()

  #7 opened 6 years ago by mkovel
  14