On Sun, Sep 11, 2011 at 8:32 PM, Andrew Hutchings <and...@linuxjedi.co.uk> wrote: >> How does that affect this issue? > > In the case of DELETE from t1; I would hope it is obvious. As part of a
Not at first. I didn't know truncate isn't transactional. So the error msg shouldn't mention truncate. What about "where true"? The optimized should eliminate it, but the safe guard would still work. > If "implicit cross joins" are things like "INNER JOIN" or "LEFT JOIN" without a ON clause, I assume they're like from A, B, C, D. Inner join is explicit. > A DELETE or UPDATE without a WHERE is valid SQL. With great power comes great responsibility. Power isn't affected, safety is. Greetings, Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
