On Wed, Oct 7, 2009 at 5:50 PM, Ronald Bradford <[email protected]> wrote: > I would have to agree with what's been said. > > You do want to be more strict. > You do want to record resulting actions, not commands.
But that *is* a record of the action -- "if the table exists, drop it." That means that on the master, that table doesn't exist, regardless of whether or not it existed before. (consider REPLACE, INSERT IGNORE and INSERT....ON DUPLICATE KEY UPDATE which are similar in that they're IF a, DO b, ELSE DO c and thus aren't "strict" statements of what changes). I'm fine with whatever happens with "IF EXISTS" and also the analog "CREATE...IF NOT EXISTS" but I think it's important to recognize that they can count as a "record of action". -Sheeri > You should be tied down to the mysql way. > > On Oct 7, 2009 5:42 PM, "Brian Moon" <[email protected]> wrote: > > On 10/7/09 3:42 PM, Sheeri K. Cabral wrote: > > oh, definitely! One of the > reasons I use "IF EXISTS... > > I think this sums it up for me. While I lean on things like this in > MySQL now, I would kind of like things to be a bit more strict. > > On 10/7/09 3:45 PM, Monty Taylor wrote: > > I do not believe it should. The > replication log in Dri... > > Yeah, I think it should be a list of changes as well. Seems "correct". > > Brian. _______________________________________________ Mailing list: > https://launchpad.net/~drizz... > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > > -- - Sheeri K. Cabral http://tinyurl.com/mysqlbook will take you to the Amazon.com page for my book, "MySQL Administrator's Bible". _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
