[ic] MYSQL/IC: Connecting to a second database

[Orko]

Thank you Mike.  I will go down that road :)

Hopping over to another thread, is there any hope in resolving Ron and
my Verisign timeout issue?

reference:
http://interchange.redhat.com/archive/interchange-users/2002/msg10340.html

-- orko

On Tue, 2002-02-26 at 11:42, Mike Heins wrote:
> Quoting Orko (orko@eacceleration.com):
> > > It is part of the default feature set (and one of the coolest things about 
> > > IC, IMHO).  Just change the relative dbconf/ files (manually typing in the 
> > > dbi, or setting a second Variable to substitute).  That is one reason why 
> > > "table" and "database" are semi-synonymous in IC.
> > 
> > 
> > What about writing to two MySQL DB's, like adding a backup mirror MySQL
> > DB, for every DB write?  Is there a central way of always mirroring DB
> > writes (not selects, of course :) ) into another DB?  I would readily
> > sacrifice the small loss in speed for the redundancy.
> > 
> > Is this just a matter of adding more dbconf files for the mirror DB
> > tables, then adding in a second import to all of the pages/routes that
> > do imports?  I'm thinking not, since there are several other ways to
> > write to the fields in the main DB...
> > 
> > Or would it be better to modify the DBI.pm module to do the second SQL
> > write statement when *any* write is detected?
> 
> Use DBD::Multiplex, which supports this without having to worry
> about it.
> 
> -- 
> Red Hat, Inc., 3005 Nichols Rd., Hamilton, OH  45013
> phone +1.513.523.7621      <mheins@redhat.com>
> 
> Be patient. God isn't finished with me yet.  -- unknown
> _______________________________________________
> interchange-users mailing list
> interchange-users@interchange.redhat.com
> http://interchange.redhat.com/mailman/listinfo/interchange-users
> 
> 
> 
> 
> 
> 
> 
-- 
Office: (360)697-1603
  Cell: (360)271-0796