Subject | RE: [IBO] Ambiguous field name? |
---|---|
Author | Steve Harp |
Post date | 2002-11-05T15:21:23Z |
How can I show you what SQL is "actually going across the wire"? Also, if I
don't have any KeyLinks defined, how can I show you what KeyLinks are being
imposed?
Thanks,
Steve
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Monday, November 04, 2002 11:20 PM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Ambiguous field name?
It's hard to tell at the moment the exact cause of the ambiguity...but
Firebird is much more fussy about join ambiguities than is InterBase...and
Jason tightened up his parsers in IBO4 some long time ago to take account
of that. Hence, in the very old version of IBO that's behind Marathon, you
are not getting this client-side bug-checking on your join columns, whereas
in IBO 4 you are. Pointing to the *exact* cause of your ambiguity error
(which is coming from the database) is impossible without knowing what SQL
is actually going across the wire.
If LocationID is a participant in a key somewhere in your structures, then
I think that your SQL as you have it now is crook. You would have mixed
SQL-89 (implicit join) syntax with SQL-92 (explicit join) syntax, which is
highly NOT recommended in any conditions but particularly in IBO.
If LocationID is part of a key in the linking of these structures, then it
should be part of the JOIN criteria, not a WHERE criterion.
It would be interesting to see your KeyLinks but, without knowing what your
database linkages ought to be, it's all so many layers of guesswork. I
guess that's the trap in trying to suggest the sources of your errors
without being supplied with the full information about the problem.
Helen
___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or InterBase
without the need for BDE, ODBC or any other layer.
___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info papers,
keyword-searchable FAQ, community code contributions and more !
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
don't have any KeyLinks defined, how can I show you what KeyLinks are being
imposed?
Thanks,
Steve
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Monday, November 04, 2002 11:20 PM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] Ambiguous field name?
It's hard to tell at the moment the exact cause of the ambiguity...but
Firebird is much more fussy about join ambiguities than is InterBase...and
Jason tightened up his parsers in IBO4 some long time ago to take account
of that. Hence, in the very old version of IBO that's behind Marathon, you
are not getting this client-side bug-checking on your join columns, whereas
in IBO 4 you are. Pointing to the *exact* cause of your ambiguity error
(which is coming from the database) is impossible without knowing what SQL
is actually going across the wire.
If LocationID is a participant in a key somewhere in your structures, then
I think that your SQL as you have it now is crook. You would have mixed
SQL-89 (implicit join) syntax with SQL-92 (explicit join) syntax, which is
highly NOT recommended in any conditions but particularly in IBO.
If LocationID is part of a key in the linking of these structures, then it
should be part of the JOIN criteria, not a WHERE criterion.
It would be interesting to see your KeyLinks but, without knowing what your
database linkages ought to be, it's all so many layers of guesswork. I
guess that's the trap in trying to suggest the sources of your errors
without being supplied with the full information about the problem.
Helen
___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or InterBase
without the need for BDE, ODBC or any other layer.
___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info papers,
keyword-searchable FAQ, community code contributions and more !
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/