Jeremy,
I did test it and couldn't get it to work one way or the otherHowever,
as it turns out, the '--binlog-ignore-db' option will work for me.
Thanks for all your help!!
Phil
At 11:03 AM 7/10/2001 -0700, you wrote:
>On Tue, Jul 10, 2001 at 09:20:35AM -0700, Philip Daggett wrote:
> > At
On Tue, Jul 10, 2001 at 09:20:35AM -0700, Philip Daggett wrote:
> At 03:01 PM 7/9/2001 -0700, you wrote:
> >On Mon, Jul 09, 2001 at 03:18:14PM -0600, Chris Bolt wrote:
> > > > We do a few large daily and monthly downloads from an Oracle database
> > > > server. Is there a way to exclude these spec
At 03:01 PM 7/9/2001 -0700, you wrote:
>On Mon, Jul 09, 2001 at 03:18:14PM -0600, Chris Bolt wrote:
> > > We do a few large daily and monthly downloads from an Oracle database
> > > server. Is there a way to exclude these specific queries from the
> > > update/binary log??
> >
> > If the queries o
On Mon, Jul 09, 2001 at 03:18:14PM -0600, Chris Bolt wrote:
> > We do a few large daily and monthly downloads from an Oracle database
> > server. Is there a way to exclude these specific queries from the
> > update/binary log??
>
> If the queries only affect one table or database, use the
> repli
> We do a few large daily and monthly downloads from an Oracle database
> server. Is there a way to exclude these specific queries from the
> update/binary log??
If the queries only affect one table or database, use the replication ignore
options listed here: http://www.mysql.com/doc/R/e/Replicat
