> The problem I see with that is that any value of accountnumber in
> public.commontable would need to be in both company1.chartoffaccounts and
> company2.chartoffaccounts. One key referencing two completely sets of
> data? That sounds broken. Can you give a more detailed example of how
> yo
Andrus wrote:
I have multi-company database.
Each company has its own chart of accounts table which are stored in each
company schema.
Some account numbers are used in a common table which is stored in public
schema.
So I need to create duplicate foreign keys like
create temp table company1.
I have multi-company database.
Each company has its own chart of accounts table which are stored in each
company schema.
Some account numbers are used in a common table which is stored in public
schema.
So I need to create duplicate foreign keys like
create temp table company1.chartoffaccounts
