Subject | When is KeyRelation necessary? |
---|---|
Author | Nando Dessena |
Post date | 2002-03-12T11:02:35Z |
Hello,
I am using a TIBOQuery with a somewhat complex SQL statement (a left
join and a "where exists" clause). The dataset is not editable unless I
set KeyRelation. I thought that it was required when using implicit join
syntax only, while I am using explicit syntax.
Does anyone have a definitive reference on when is KeyRelation
necessary?
The query is something like that:
select a.*, b.id
from a left join b on (a.id = b.id)
where exists (select s.id from some_stored_procedure(:a_param) s where
s.id = a.id)
order by a.id
I have set KeyLinks to 'a.id', and thought that would be enough.
Setting KeyRelation to 'a' does work well, so it's not really an issue
for me, just a curiosity.
Ciao
--
____
_/\/ando
I am using a TIBOQuery with a somewhat complex SQL statement (a left
join and a "where exists" clause). The dataset is not editable unless I
set KeyRelation. I thought that it was required when using implicit join
syntax only, while I am using explicit syntax.
Does anyone have a definitive reference on when is KeyRelation
necessary?
The query is something like that:
select a.*, b.id
from a left join b on (a.id = b.id)
where exists (select s.id from some_stored_procedure(:a_param) s where
s.id = a.id)
order by a.id
I have set KeyLinks to 'a.id', and thought that would be enough.
Setting KeyRelation to 'a' does work well, so it's not really an issue
for me, just a curiosity.
Ciao
--
____
_/\/ando