tediousjs/tedious-connection-pool

Issues

• Support tedious 2.0.1?

  #43 opened 7 months ago by vangorra
  3

• request.transformIntoExecuteSqlRpc() is not a function

  #63 opened 3 years ago by JaggieG
  3

• Is this project dead?

  #61 opened 4 years ago by ermamud
  7

• Pool fills up with 'USED' connections - node app restart required as a result

  #56 opened 5 years ago by Slos
  1

• Draining the pool after releasing connections may cause write to destroyed stream

  #58 opened 5 years ago by irgijs
  3

• TypeError: cb is not a function

  #60 opened 5 years ago by notestyle
  2

• new maintainer ?

  #48 opened 6 years ago by spanditcaa
  4

• Timeouts don't seem to work as expected

  #57 opened 5 years ago by Slos
  0

• Pause()/resume() doesn't work as expected with connection from connectionPool

  #55 opened 5 years ago by niranjan1001
  0

• 1.0.5 release may be incompatible with tedious 5.x release

  #54 opened 5 years ago by BrianLawton
  1

• Issue with connection closed

  #37 opened 8 years ago by PeterNierop
  13

• ConnectionError: Failed to connect to <server name> in 15000ms

  #53 opened 6 years ago by aniltomar10
  0

• Allow prepared statements to persist across returning a connection to the pool

  #46 opened 7 years ago by andrewsensus
  2

• Multiple Request On Multiple Connection

  #49 opened 6 years ago by npshubh
  1

• Incompatibility with Rollup

  #51 opened 6 years ago by chdh
  1

• Error: connection.release is not a function

  #50 opened 6 years ago by vincebanzon
  1

• Requests can only be made in the LoggedIn state

  #35 opened 8 years ago by nvsoares
  7

• Acquire calls do not timeout if pool is drained.

  #42 opened 8 years ago by TheFarmer1
  0

• error thrown in tedious-connection-pool when calling release()

  #41 opened 8 years ago by mcrummey
  2

• Error: Acquire Timeout Exceeded for queued queries.

  #40 opened 8 years ago by ankurgupta4891
  6

• Update memory-usage test to add validation.

  #38 opened 8 years ago by tvrprasad
  2

• get connection Status, pool.acquire method is the only way?

  #36 opened 8 years ago by aeolusheath
  4

• Add Exponential Backoff mechanism

  #33 opened 8 years ago by gkorland
  3

• Cannot call method 'close' of undefined

  #27 opened 8 years ago by leibale
  5

• Tedious connection.release() messes up newrelic error log

  #32 opened 8 years ago by o-e
  1

• What happens on connection timeout?

  #29 opened 8 years ago by akc42
  3

• How to fill the pool with different connections?

  #26 opened 9 years ago by boredSinan
  4

• connection pool doesn't not respect request callback on socket error

  #23 opened 9 years ago by ashelley
  1

• connections not releasing properly

  #22 opened 9 years ago by fryeguy63
  4

• drain() does not release all (network) resources

  #21 opened 9 years ago by jdonnerstag
  2

• drain callback not always invoked

  #20 opened 9 years ago by jdonnerstag
  1

• Exception

  #19 opened 9 years ago by NoumanSaleem
  3

• I can't listen the 'done' event

  #18 opened 9 years ago by SergioGeeK7
  2

• Overriding max doesn't change min

  #16 opened 9 years ago by lloydcotten
  2

• Tests not up to date.

  #11 opened 10 years ago by yasen-atanasov
  1

• Memory leak when DB connection is temporarily lost.

  #12 opened 10 years ago by yasen-atanasov
  3

• opening too many connections kill tedious driver

  #15 opened 9 years ago by bergerdenes
  1

• Keep getting acquire Timeout error

  #13 opened 10 years ago by iamtennislover
  7

• Connection Issues

  #5 opened 10 years ago by kimi23
  0

• Connecting to remote Sql Server using node tedious

  #4 opened 10 years ago by kimi23
  0

• response.write on Tedious connection pool

  #6 opened 11 years ago by catoszyrko
  5

• having difficulty obtaining a connection from the pool

  #3 opened 12 years ago by nicktackes
  5

• tag a first version

  #2 opened 12 years ago by e11137
  1