Korinne Adler
Korinne Adler
This is not needed for v1.0, moving to v1.1
As @abmusse said, we plan to support iSql for some time and the SQL capabilities of XMLSERVICE aren't going away so I suppose one could always generate the XML themselves...
Ahh, right. I forgot that the Node version of this package opens its own connection and closes it every time you call it. I've definitely had that idea, perhaps we...
That might be a good workaround, but ideally we shouldn't be using deprecated methods internally (except inside methods that are deprecated themselves).
> Also parameters can be customized at an individual level by passing an object within the params Array. Looks like a lot of this function requires using the old API....
Each connection and statement object requires a CLI database handle. CLI has a max limit of 32k handles per job, so conceivably the absolute max connections you could get is...
AFAIK you cannot inspect the number of open CLI handles from anywhere. I don't think CLI keeps a count or anything - it's just if you try to allocate one...
There are a lot of interesting points to dive in to in regards to threading and whatnot, but I don't have time to look at those at the moment. AFAIK,...
Could be done, but we'd need to make `attach` return a Promise. Basic design: - pool has two new internal attributes: a list of waiters and an an [EventEmitter](https://nodejs.org/api/events.html) instance...
We'll need to set up labels to keep things open, see https://github.com/actions/stale/blob/master/action.yml#L21