Open GoogleCodeExporter opened 9 years ago
GHost++ automatically reconnects to the database when a connection is lost. In
fact,
GHost++ uses several connections to the database, one per simultaneous query.
This
normally results in 22 simultaneous connections at the end of each 5v5 DotA game
although these connections are reused for future games.
However, if a connection is interrupted while a query is in progress GHost++
will not
attempt to retry the query and data will be lost. This is unlikely to be fixed
and is
certainly worth classifying as a defect. I will accept this issue as low
priority but
it may not be resolved anytime soon.
Original comment by hogantp
on 17 Jul 2009 at 6:39
Original comment by hogantp
on 17 Jul 2009 at 6:41
one the best things to do to avoid this i know is to run a mysql locally
Original comment by Absolute...@gmail.com
on 18 Jul 2009 at 4:16
I am currently working on a side project that will require a queue system for a
single
MySQL connection. I might give GHost++ a patch in the future about this issue
and reuse
the code I've done.
Original comment by ManhimOne
on 19 Feb 2010 at 5:37
Hello. Is it a progress under this mysql problem? It's very important thing,
please give us a patch!
Original comment by megli...@gmail.com
on 16 Jun 2010 at 10:40
I won't promise anything soon. I've been very busy with life and I am still.
I'll throw a patch probably for GHost++ CB with Instinct121 since GHost++ have
been discontinued.
Original comment by ManhimOne
on 21 Jun 2010 at 1:53
A queue system sounds nice but will it work for just a single connection?
All I know is, ghost++ needs some mysql optimization. My mysql process goes
nuts..
Original comment by theha...@gmail.com
on 17 Feb 2011 at 11:40
That's retarded to have established 32 MySQL connections. I've been dealing
with MySQL for several years and never have come across an application that
depends on 32 different MySQL queries.
This is by far one of the most memory consuming applications (as far as mysql
goes) I've seen. Only three, and maybe 4, mysql persistent sockets is needed to
do carry out the functionality of this application.
Original comment by ccarve...@gmail.com
on 22 Apr 2011 at 7:56
I'd say that this is by far not the most crucial problem with
mysql and ghost implementation overall!
I can't give you a hint and outputs now, cuz my ghost now doesn't have such
uptime yet.
Original comment by random...@gmail.com
on 25 Oct 2012 at 7:05
Original issue reported on code.google.com by
termit1...@rambler.ru
on 5 Jul 2009 at 11:13