Yup.
Having someone implement this would be great!
Note: sync'ing the two databases is going to be difficult.
You are also going to have problems with telling the difference between a
connection A object which has just had problems getting a connection to
database A and a connection B object which is still connected to database A.
In other words, you may end up with accidentally connecting to the database
B when you didn't really need to. The way around this is to attempt to use
up all of the connections to database A before moving on to database B. You
also need something to "reset" the cache so that when database A comes back
up, it will start using it again. A background thread can deal with that.
-jon
on 7/23/01 2:03 AM, "Kasper Nielsen" <[EMAIL PROTECTED]> wrote:
> Hasn't been done yet.
>
>> From http://jakarta.apache.org/turbine/todo.html (List is out of date)
>
> a.. Add a feature to the connection pool system to allow it to have multiple
> database fail over so that if all the connections to one database fail, it
> will auto-attempt to connect to a "backup" database.
> Owner: None
>
> You should look at the DB service if you want to do anything.
>
> - Kasper
>
>
> ----- Original Message -----
> From: "Cromer, Deborah" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 23, 2001 8:55 AM
> Subject: redundant database
>
>
>> Hi,
>>
>> For my application I am setting up two databases for redundancy. I plan on
>> having two-way redundancy, using MySQL.
>>
>> I was wondering if there is a way of setting up a seconday database in
>> Turbine so that if the default database is down the secondary one gets
> used.
>>
>> Is something like that already written? Or where should I stick it in
>> myself?
>>
>> Deborah
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
