Expression index may not be used by the optimizer if created and used in
different connection charsets
------------------------------------------------------------------------------------------------------
Key: CORE-5122
URL: http://tracker.firebirdsql.org/browse/CORE-5122
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.5.5, 3.0 RC1, 3.0 Beta 2, 2.5.4, 3.0 Beta 1, 2.5.3, 3.0
RC2
Reporter: Dmitry Yemanov
If the index expression contains a string literal, e.g. computed by
(my_udf(my_field, 'ABC')) or computed by (my_field || 'ABC'), index is created
in connection charset X but used in connections with charset other than X, then
index and user expressions are considered different and index is not used by
the optimizer.
This is a regression introduced in v2.5.3 as well as in v3.0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
