deterministic mysql_MySQL中的确定性函数

最新推荐文章于 2024-07-05 07:00:00 发布

weixin_39587407

最新推荐文章于 2024-07-05 07:00:00 发布

阅读量496

点赞数

文章标签： deterministic mysql

本文链接：https://blog.csdn.net/weixin_39587407/article/details/113208863

版权

MySQL中的确定性函数是指对于相同的输入参数总是返回相同结果的函数。然而，如果函数内部包含如查询表的数据这样的行为，则可能因并发操作而变得非确定。尽管存在误解，MySQL不会检查声明为DETERMINISTIC的函数是否真的确定。错误声明可能会导致优化器选择错误的执行计划或性能下降。

摘要由CSDN通过智能技术生成

I got confused with a seemingly simple concept. Mysql defines deterministic function as a function that

always produces the same result for the same input parameters

So in my understanding, functions like

CREATE FUNCTION foo (val INT) READS SQL DATA

BEGIN

DECLARE retval INT;

SET retval = (SELECT COUNT(*) FROM table_1 WHERE field_1 = val);

RETURN retval;

END;

are not deterministic (there is no guarantee that delete/update/insert does not happen between 2 calls to the function). At the same time, I saw many functions which do pretty much the same, i.e. return value based on result of queries, and declared as DETERMINISTIC. It looks like I'm missing something very basic.

Could anyone clarify this issue?

Thanks.

Update

Thanks for those who answered(+1); so far it looks like there is a widespread misuse of DETERMINISTIC keyword. It is still hard to believe for me that so many people do it, so I'll wait a bit for other answers.

解决方案

From the MySQL 5.0 Reference:

Assessment of the nature of a routine is based on the “honesty” of the creator: MySQL does not check that a routine declared DETERMINISTIC is free of statements that produce nondeterministic results. However, misdeclaring a routine might affect results or affect performance. Declaring a nondeterministic routine as DETERMINISTIC might lead to unexpected results by causing the optimizer to make incorrect execution plan choices. Declaring a deterministic routine as NONDETERMINISTIC might diminish performance by causing available optimizations not to be used. Prior to MySQL 5.0.44, the DETERMINISTIC characteristic is accepted, but not used by the optimizer.

So there you have it, you can tag a stored routine as DETERMINISTIC even if it is not, but it might lead to unexpected results or performance problems.