Archives of the TeradataForum

Message Posted: Mon, 05 Dec 2005 @ 16:53:47 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I think the better way is EXPLAIN should not be checked for SELECT, UPDATE, ..., permission. For implementation, there can be a flag that will tell the database if issuer permission should be checked or not before the query reaches the optimizer. Or, add a explain privilege that only allows to generate an execution plan. Anyway, the real data will not be seen or changed.

Because the development databases usually do not have a large set of data, and/or statistics, you cannot expect the development and production databases will provide the same execution plan. For syntax checking, it can be done on a development database.

Sometimes it is easy to make a mistake after a long day work, ex. Missing "EXPLAIN". If it is a update, it can be disastrous. If the user can only use explain, he/she will not be able to run "UPDATE". UPDATE cannot be executed because lack of permission. That way, developers can generate execution plans without touching data.

	<Prev	Next>		<<First	<Prev	Next>	Last>>