Subject | Re: [firebird-support] Why PLAN token is not allowed after ORDER BY? |
---|---|
Author | Mark Rotteveel |
Post date | 2012-06-03T08:03:07Z |
On 2-6-2012 23:17, Dmitry Kuzmenko wrote:
asking why Firebird does not accept a PLAN after ORDER BY, but it does
before ORDER BY.
I think the reason is simply that the grammar definition of Firebird
expects it before the ORDER BY. There is probably nothing more to it.
Telling people they are stupid (my interpretation of your messages) is
not helpful.
Mark
--
Mark Rotteveel
> Hello, Alec!Dmitry, I think this is not a very constructive way to respond. Alec is
>
> AS> The question is why FB complains about PLAN token after ORDER BY clause?
>
> the answer is that PLAN is wrong. ORDER BY in query affects PLAN, it
> will contain PLAN SORT or TABLE ORDER INDEX specification. Your PLAN
> specification is crap, sorry for rude answer.
> As I said before, you need to know how Firebird produces plan
> specification and how it accepts it.
asking why Firebird does not accept a PLAN after ORDER BY, but it does
before ORDER BY.
I think the reason is simply that the grammar definition of Firebird
expects it before the ORDER BY. There is probably nothing more to it.
Telling people they are stupid (my interpretation of your messages) is
not helpful.
Mark
--
Mark Rotteveel