Re: Unique Primary Key Linked to Multiple Accounts - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Unique Primary Key Linked to Multiple Accounts
Date
Msg-id e4fd0ae1-ab0a-4b83-90aa-12ee4e0ebc23@aklaver.com
Whole thread Raw
In response to Re: Unique Primary Key Linked to Multiple Accounts  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On 11/13/23 08:45, Adrian Klaver wrote:
> On 11/12/23 23:02, Anthony Apollis wrote:
>> Please advice. I brought in data from SAP and assigned unique primary 
>> key to the table:
>>
> 
>>
>> I joined it with a dimension table.
>>
>> Joining code
>>
>> fact."IMETA_ZTRB_MP$F_ZTBR_TA_BW"ASfact
>> LEFTJOINdim."IMETA_BRACS_Mapping"ASbracs_map
>> ONfact."Account_Number"=bracs_map."GCoA"ANDfact."Expense_Type"=bracs_map."EXPENSE FLAG"
>>
>> It is joined on the Account numbers, which appears in the table 
>> multiple times. Problem is the Unique Primary Key is then mapped to 
>> these Account numbers multiple times.
> 
> This is not a problem it is the nature of the table definitions and the 
> query. The PK is "ZTBR_TransactionCode", but you are joining on 
> fact."Account_Number"=bracs_map."GCoA"ANDfact."Expense_Type"=bracs_map."EXPENSE FLAG". Since you indicate that there
aremultiple account numbers in the table then it is no surprise that the "ZTBR_TransactionCode" is repeated.
 

Aah, that should be '... multiple repeated account numbers in the table ...'
> 
> 
>> Please advice.
>>
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Unique Primary Key Linked to Multiple Accounts
Next
From: Tom Lane
Date:
Subject: Re: Is "WITH RECURSIVE" limited to the first position of CTEs by design?