upgrade 5.0.51 to 5.1.36 - TRUNCATE/DROP on temp table?

mysql list,

after my upgrade to 5.1.36 I hit this odd little problem:=20

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 th=
e
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.


/Per Jessen, Zürich


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: upgrade 5.0.51 to 5.1.36 - TRUNCATE/DROP on temp table?

Per Jessen wrote:

> mysql list,
>=20
> after my upgrade to 5.1.36 I hit this odd little problem:
>=20
> I have an application which does roughly this:
>=20
> CREATE TEMP TABLE new LIKE old;
> populate 'new'.
> do some stuff
> TRUNCATE new;
> populate again
>=20
> This has always worked fine, but after the upgrade it failed because
> the user does not have DROP authority on 'new'. Can anyone explain t=
o
> me what causes this change in behaviour? For the time being I've
> changed the TRUNCATE to a DELETE.
>=20

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


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg