At 07:39 AM 9/09/2003 +0000, you wrote:

>This is example SQL:
>select TABLE_1.NAME, TABLE_2.NAME, TABLE_3.NAME, TABLE_2.LENGTH,
>TABLE_2.LANGUAGE_ID
>from TABLE_4
>join TABLE_1 on TABLE_1.ID = TABLE_4.T1_ID
>join TABLE_2 on TABLE_2.ID = TABLE_4.T2_ID
>join TABLE_3 on TABLE_3.ID = TABLE_2.T3_ID
>where TABLE_4.T2_ID = :T2_ID
>
>This one is called for different parameters ':T2_ID'.
>I though that I maybe should put join clauses into 'JoinLinks'
>property...?

No: you never use JoinLinks with the explicit JOIN syntax. It has a very
specific purpose, which is to distinguish WHERE criteria from JOIN criteria
in implicit join statements.

This is a very horrible query, by the way. Not only does the output set
have no columns from TABLE_4, but you have made TABLE_4 the controlling
table of the query. I simply do not believe this was ever *fast* in the BDE.

From IBO's point of view (and all common sense) it is impossible to get
column-based KeyLinks for this set. Amongst other things, IBO uses
KeyLinks for determining the cursors it uses to set "windows" in datasets,
to optimise the traffic between the server and the client. It's true to
say that IBO rewards good query design.

If this is typical of the SQL that isn't performing well, this seems like a
good point in your life to brush up on your query specification technique.

Helen