On 07/15/2010 04:11 PM, Markus Hoenicka wrote:
> I assume that the server going away is a problem of all database engines,
> except maybe the
> embedded ones. Adding some code to the MySQL driver to fix your
> original problem thus might be the wrong solution. Don't you
> experience the same pro
Vikram Ambrose writes:
> There is indeed enough information to find this scenario. Here is a very
> simple callback I use at the moment:
>
> void DB_error_callback(dbi_conn conn, void *udata){
> int rv;
> const char *errormsg = NULL;
>
> rv = dbi_conn_error(DB_conn,&errorm
On 07/01/2010 03:12 AM, Markus Hoenicka wrote:
> Vikram Ambrose was heard to say:
>
>> Is there a way of having the mysql driver, reconnect and then complete
>> the query without erroring out, in the case of driver/server timeout?
>> This way I do not lose my query to a timeout or need to have som
Vikram Ambrose was heard to say:
> Is there a way of having the mysql driver, reconnect and then complete
> the query without erroring out, in the case of driver/server timeout?
> This way I do not lose my query to a timeout or need to have some sort
> of global command buffer that the callback w
I make use of the mysql driver and I find that when I come back to my PC
the next day, the first query I issue always results in an error. I need
to reconnect to the server for it to work again.
I've setup a callback to do the reconnect, but the original query is lost.
Is there a way of having
