Subject Re: [firebird-support] Why PLAN token is not allowed after ORDER BY?
Author Alec Swan
I am sorry for the last post I did not see that Mark already answered it.

Is there online docs for SELECT syntax?

Thank you, Mark.

On Sun, Jun 3, 2012 at 8:59 AM, Alec Swan <alecswan@...> wrote:

> Thanks, Mark.
>
> I found FB 2.5 SQL Language reference here
> http://www.firebirdsql.org/refdocs/langrefupd25-select.html but it does
> not contain the grammar for the entire SELECT statement, just individual
> fragments, such as JOIN, ORDER BY, etc.
>
> Where can I find a comprehensive syntax definition for the entire SELECT
> statement?
>
> Thanks,
>
> Alec
>
>
> On Sun, Jun 3, 2012 at 2:03 AM, Mark Rotteveel <mark@...>wrote:
>
>> **
>>
>>
>> On 2-6-2012 23:17, Dmitry Kuzmenko wrote:
>> > Hello, Alec!
>> >
>> > 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.
>>
>> Dmitry, I think this is not a very constructive way to respond. Alec is
>> 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
>>
>>
>>
>
>


[Non-text portions of this message have been removed]