Hi,
That's an interesting issue and definitely a problem. In our particular
case, however, it is not relevant because we have a load balancer and a
forward routing proxy between the client and the actual server process
we're attempting to restart.
Well actually my bad, we also use a proxy.
.
>
> I was half way through doing this, when I read this:
>
> https://github.com/nodejs/node/issues/2642
>
> How do you deal with keepalive connections? They can potentially stay up
> forever (if they ping often enough) even after close() has been issued...
>
That's an interesting issue and
I recommend you, to start using sequelize
https://juststartworking.com/sequelize-how-to-properly-order-a-nested-query-with-include/
On Thu, Mar 2, 2017 at 11:07 AM, Paul Spaulding wrote:
> Without further information, it is impossible to know what you are
> asking.
Without further information, it is impossible to know what you are asking.
Perhaps are looking for something like this:
http://knexjs.org/
It works with MySQL (among others) and supports very complex queries.
On Wednesday, March 1, 2017 at 12:11:46 PM UTC-5, Vishal Yadav wrote:
>
> Hello
Hi Tony.
Have you ever considered using a firewall and routing approach?
For example, on the same server, you can keep open your current node-js
server and open other in the port 81, for example.
And the trick is, *send only the new users connections *to the new node-js
server in the port 81.
You need to be specific and provide more details. Include the query, the
code you are using to execute the query and the modules you are using, and
the error you are having.
On Wednesday, 1 March 2017 22:41:46 UTC+5:30, Vishal Yadav wrote:
>
> Hello All,
>
> Actually I'm integration node js