Re: Columns in USING clause for join don't appear in SELECT *?

O.k., that worked, but the logic behind the "fix", as you put it, escapes
me. I can understand that the two sources of the same column name in a
USING clause will have identical values, so it's not *necessary* to qualify
them. But why is it desirable that those columns should be removed from the
c.* reference? What did the "fix" actually fix?

- Dan

On Thu, May 10, 2018 at 4:46 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

WAF....(working as fixed) ;)

You've only asked for c.*

But the join columns aren't seen as part of C or D anymore...

This would fail
select c.su_ID1 from Test4Dupes JOIN Charges c
using (su_ID1, su_ID2, su_ID3, su_DoS);

You'll have to add the using columns explicity

select su_ID1, su_ID2, su_ID3, su_DoS, c.*
from Test4Dupes JOIN Charges c
using (su_ID1, su_ID2, su_ID3, su_DoS);

Charles

On Thu, May 10, 2018 at 2:30 PM, Dan <dan27649@xxxxxxxxx> wrote:

Going a little crazy here. Running the following query, all of the

columns

from Charges are shown EXCEPT for columns in the USING clause. Is this
expected behavior?

select c.* from Test4Dupes JOIN Charges c
using (su_ID1, su_ID2, su_ID3, su_DoS);

FWIW, v7r1 with somewhat recent PTF groups applied. Also, same behavior

in

STRSQL and ACS Run SQL Scripts.

- Dan