Subject | Re: How select against a sub-select field? |
---|---|
Author | mmenaz |
Post date | 2002-04-17T22:04:19Z |
--- In ib-support@y..., Svein Erling Tysvær <svein.erling.tysvaer@k...> wro=
te:
that make it sure. The sql code, anyway, is just a sample for the problem, a=
nd the problem is: how can I reference *that* field (that comes from the sub=
select)? If I can read it, if I have it's name displayed in the result set, =
if it seems to be a "regular" field, why can't I select it's value? I know t=
hat a join does the trick, but is this behaviour correct, or it's a bug?
Thanks
Marco Menardi
te:
> Marco,o
> I don't quite understand your SQL. I normally use subselects when I want
> the row to appear even if there's no match for the subselect, but in your=
> case it seems like you always want it to match and then there's no need t=
> make it a subselect.I *do* know that there is a matching record, there are database constrains =
that make it sure. The sql code, anyway, is just a sample for the problem, a=
nd the problem is: how can I reference *that* field (that comes from the sub=
select)? If I can read it, if I have it's name displayed in the result set, =
if it seems to be a "regular" field, why can't I select it's value? I know t=
hat a join does the trick, but is this behaviour correct, or it's a bug?
Thanks
Marco Menardi