----- Original Message -----
> From: "ANIL YADAV" <uranil@stripped>
> Is there no way to deal the situation ? As change is application Will
> take a long time..
I would assume that restarting your application would recreate the table on the master,
and thus also on the slave.
If that's not an option, but you're sure that there's only on connection from your
application you could manually create the table on the slave, thus allowing replication
to continue. That will not interfere with application startup, as a create temporary
table statement naming an existing table will actually succeed and temporarily hide the
permanent table of the same name; but you do need to make sure your application does not
rely on the connection-specific nature of temporary tables, as all connections will see
the same table, and that could cause wrong data to be used (two sessions writing private
data into the same tabie...)
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel
