Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
ListSqlOperatorTable is inefficient if it contains a large number of operators. It currently examines the operators one by one. ReflectiveSqlOperatorTable (and its subclass, SqlStdOperatorTable) builds a map of operators by name (actually two maps, one case-sensitive and one case-insensitive).
ListSqlOperatorTable should do the same, at least in its immutable form.
Attachments
Issue Links
- relates to
-
CALCITE-5153 Create an immutable version of ListSqlOperatorTable
- Closed
- links to