Subject | Re: select SP & KeyLinks problem |
---|---|
Author | Gediminas |
Post date | 2003-11-21T17:37:46Z |
--- In IBObjects@yahoogroups.com, Lucas Franzen <luc@r...> wrote:
to identify each row, so it could be used as dataset PK - so it suits
for KeyLinks - maybe I'm wrong in SP case, I don't know. But if I make
direct select from joined tables, I can set KeyLinks without
restrictions, so guessed, that this is true and for SP
code, for example, so asked, is SUSPEND needed, that's all:
EXCEPTION WRONG_ID;
SUSPEND;
Gediminas
> But you cannot have KeyLinks to a storedproc, since you're notselecting
> directly on the relation (table) but do it via kind of an intermediateOk, but stored procedure selects dataset, where Teisejo_ID is unique
> record set (the stoered procedure).
> So even if Teisejo.ID is your primary key it is the primary key in the
> table not in the stored proc (they don't have primary keys).
>
> Set the keylinks property to autodefine.
> And set the RequestLive property to false - this should help.
to identify each row, so it could be used as dataset PK - so it suits
for KeyLinks - maybe I'm wrong in SP case, I don't know. But if I make
direct select from joined tables, I can set KeyLinks without
restrictions, so guessed, that this is true and for SP
> > If SP raises exception, SUSPEND is needed or not?I saw an example, where SUSPEND was wrote down after exception raise
>
> What do you mean by that?
code, for example, so asked, is SUSPEND needed, that's all:
EXCEPTION WRONG_ID;
SUSPEND;
Gediminas