Op 10-10-2013 8:51, Marc Schmitzer schreef:
> On 10/09/2013 04:46 PM, S R wrote:
>> In a similar situation, if I recall correctly, we elected to open the
>> database connection each time we needed it. Through testing we found
>> that connection pooling in the the underlying infrastructure (windows
On 10/09/2013 04:46 PM, S R wrote:
>
> In a similar situation, if I recall correctly, we elected to open the
> database connection each time we needed it. Through testing we found
> that connection pooling in the the underlying infrastructure (windows,
> using oracle and ms sqlserver) worked well
In a similar situation, if I recall correctly, we elected to open the
database connection each time we needed it. Through testing we found that
connection pooling in the the underlying infrastructure (windows, using
oracle and ms sqlserver) worked well. The reconnection cost was usually
trivial c
On 10/09/2013 12:27 PM, Marc Schmitzer wrote:
> While this works well most of the time, we occasionally have queries
> fail with "MySQL server has gone away" errors. We know that the mysqld
> process has indeed *not* gone away, and re-opening the connection works.
Ok, this appears to be caused by
On 9 October 2013 11:27, Marc Schmitzer wrote:
> While this works well most of the time, we occasionally have queries
> fail with "MySQL server has gone away" errors. We know that the mysqld
> process has indeed *not* gone away, and re-opening the connection works.
>
> My theory is that the initia
Hi list,
my team develops a relatively long-running (normally 10+ hours, during
development for days or even weeks) Qt application that uses a MySQL
database.
The usage pattern the database connection looks like this:
At startup:
- db = QSqlDatabase::addDatabase(connection_name)
- configure ho
