| Subject | Re: [firebird-support] Why PLAN token is not allowed after ORDER BY? |
|---|---|
| Author | Dmitry Kuzmenko |
| Post date | 2012-06-02T20:30:18Z |
Hello, Alec!
Saturday, June 2, 2012, 11:28:52 PM, you wrote:
AS> Hello,
AS> I am using FB 2.5 and execute SQL using Flamerobin. I am trying to
AS> specify a plan for a query that has ORDER BY clause. I get a "invalid
AS> token PLAN" error if I specify the plan after ORDER BY, but it works
AS> OK if I specify the plan before ORDER BY. But the plan contains
AS> instructions for ORDER BY as well. What's the problem?
1. do not use PLAN in queries until you fully understand how optimizer
uses indices, etc.
2. who created your indices, with the names like
"IDX_214/CmDhH936xtHXcXNQKg==" ?
--
Dmitry Kuzmenko, www.ib-aid.com
Saturday, June 2, 2012, 11:28:52 PM, you wrote:
AS> Hello,
AS> I am using FB 2.5 and execute SQL using Flamerobin. I am trying to
AS> specify a plan for a query that has ORDER BY clause. I get a "invalid
AS> token PLAN" error if I specify the plan after ORDER BY, but it works
AS> OK if I specify the plan before ORDER BY. But the plan contains
AS> instructions for ORDER BY as well. What's the problem?
1. do not use PLAN in queries until you fully understand how optimizer
uses indices, etc.
2. who created your indices, with the names like
"IDX_214/CmDhH936xtHXcXNQKg==" ?
--
Dmitry Kuzmenko, www.ib-aid.com