Hi,
I think we should move to private because this is getting OT.

This 'feature' of selecting a generator is a legacy from old programmers
around here.
It's because the procedure GET_FILHOS_TAREFA returns a tree structure like
ID; PARENT_ID; CAPTION with the *correct hierarchical order*.
I'm using Delphi/Midas with IBX, so our BuildHierarchicTree procedure in
delphi (that work with a TVirtualTreeView) needs the data ordered by the
fetch order. The ClientDataSet component from Midas only obey the order of
indexes. Then i can't order by ID or other fields. So we get this "ROW_ID"
to put an index on it. Doesn't matter the value that will be in this field,
what matter is the sequence it will have.

We could have put a field 'order' at the stored procedure source, returning
a field called 'row_id' but this will be done when we reach the
'optimization time' on the project.

This generator is set to zero from times to times (when any client
application starts)

----- Original Message -----
From: "Alan McDonald" <alan@...>
To: <ib-support@yahoogroups.com>
Sent: Monday, May 05, 2003 7:49 PM
Subject: RE: [ib-support] Ambiguous field


> > select
> > cast(gen_id(GEN_ROW_ID, 1) as INTEGER) ROW_ID,
> > GFT.PATH,
>
> Why are you selecting a generator? I've never seen (or even thought to do
> this) before
>
> Alan
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>