Dmitry,

We create indexes programmatically and we we generate their names based on
their definition, such the columns they index. In fact the plan I am trying
to force the query optimizer to use is exactly the plan that was generated
by query optimizer when I replaced INNER with LEFT JOIN in the query.

COPY is the name of the table.

The question is why FB complains about PLAN token after ORDER BY clause?

Thanks,

Alec

On Sat, Jun 2, 2012 at 2:31 PM, Dmitry Kuzmenko <kdv@...> wrote:

> **
>
>
> Hello, Alec!
>
> Saturday, June 2, 2012, 11:28:52 PM, you wrote:
>
> 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> COPY INDEX ("PK_ZM6SRonqR8AHSQuCISgvnQ=="))
>
> and, finally, who told you about "COPY" word in a plan,
> or where you got it?
>
> --
> Dmitry Kuzmenko, www.ib-aid.com
>
>
>


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