Sent: Tuesday, January 14, 2003 6:18 PM
> To: Ross Davis - DataAnywhere.net
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Design feature or bug
>
>
> On Tue, Jan 14, 2003 at 04:41:53PM -0800, Ross Davis -
> DataAnywhere.net wrote:
> >
> >
> &
On Tue, Jan 14, 2003 at 04:41:53PM -0800, Ross Davis - DataAnywhere.net wrote:
>
>
> I stand corrected. In a production environment a stopped server is as
> good as crashed.
Ah, good.
> I know why things work they way they do, but it would be nice to have an
> option to change the replication
> -Original Message-
> From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 14, 2003 4:00 PM
> To: Ross Davis - DataAnywhere.net
> Cc: [EMAIL PROTECTED]
> Subject: Re: Design feature or bug
>
>
> On Tue, Jan 14, 2003 at 0
On Tue, Jan 14, 2003 at 02:43:27PM -0800, Ross Davis - DataAnywhere.net wrote:
> I have a 3.23.53 server that is a slave of another 3.25.52 server.
> Master has 2 databases on it.
>
> On the slave only only one of the databases is replicated.
>
> If I reference the table database that is not on
I have a 3.23.53 server that is a slave of another 3.25.52 server.
Master has 2 databases on it.
On the slave only only one of the databases is replicated.
If I reference the table database that is not on the slave during an
insert or something on the server it crashes the slave!
Shouldn't the
