On Sunday 04 June 2006 20:33, Stipe Tolj wrote:: > Rene Kluwen wrote: > > I will choose b) which is most flexible and also takes care of restarted > > mysqld's. > > > > I will try to fix this one of these days... but... Isn't this something > > that dbpool (in particular dbpool_consume) should take care of? > > I was expecting this should go automatically... in the same manner as > > bearerbox does the trick. > > yep, you're right. The abstraction layer should take care. > > The application layer (sqlbox) should relly that there is a connection, if > a connection is possible. dbpool would have to take care for this. > > Stipe
so how can we get rid of this bug? I assume this is a bug because the whole thing stops working... or a least a workaround?
