1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

parser optimization

Browse Source 
first try to resolve the function name as a native function,
and only then look within pluggable data types
This commit is contained in:
Sergei Golubchik 2020-09-17 16:08:23 +02:00
parent d8fbd463a0
commit 3cd4d8ddba
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
sql/sql_yacc.yy
View File

@ -10594,19 +10594,20 @@ function_call_generic:
names are resolved with the following order: names are resolved with the following order:
- MySQL native functions, - MySQL native functions,
- User Defined Functions, - User Defined Functions,
- Constructors, like POINT(1,1)
- Stored Functions (assuming the current <use> database) - Stored Functions (assuming the current <use> database)
This will be revised with WL#2128 (SQL PATH) This will be revised with WL#2128 (SQL PATH)
*/ */
if ((h= Type_handler::handler_by_name(thd, $1)) && if ((builder= find_native_function_builder(thd, &$1)))
(item= h->make_constructor_item(thd, $4)))
{
// Found a constructor with a proper argument count
}
else if ((builder= find_native_function_builder(thd, &$1)))
{ {
item= builder->create_func(thd, &$1, $4); item= builder->create_func(thd, &$1, $4);
} }
else if ((h= Type_handler::handler_by_name(thd, $1)) &&
(item= h->make_constructor_item(thd, $4)))
{
// Found a constructor with a proper argument count
}
else else
{ {
#ifdef HAVE_DLOPEN #ifdef HAVE_DLOPEN