Per Jessen wrote:
> mysql list,
>
> after my upgrade to 5.1.36 I hit this odd little problem:
>
> I have an application which does roughly this:
>
> CREATE TEMP TABLE new LIKE old;
> populate 'new'.
> do some stuff
> TRUNCATE new;
> populate again
>
> This has always worked fine, but after the upgrade it failed because
> the user does not have DROP authority on 'new'. Can anyone explain to
> me what causes this change in behaviour? For the time being I've
> changed the TRUNCATE to a DELETE.
>
I get to answer that one myself - from the manual:
"Beginning with MySQL 5.1.16, the DROP privilege is required for
TRUNCATE TABLE (before that, TRUNCATE TABLE requires the DELETE
privilege). "
/Per Jessen, Zürich
