Re: Using a Conversion Table - Mailing list pgsql-general

From David G. Johnston
Subject Re: Using a Conversion Table
Date
Msg-id CAKFQuwY+iKAybHFBafVj6Va0oC3U2rAYX9Cw3VKvuAa-L76veg@mail.gmail.com
Whole thread Raw
In response to Using a Conversion Table  (Anthony Apollis <anthony.apollis@gmail.com>)
List pgsql-general
On Wednesday, February 14, 2024, Anthony Apollis <anthony.apollis@gmail.com> wrote:

Conversion Table :


CREATE TABLE IF NOT EXISTS dim."IMETA_Master_Currency_Data_TA_BR"
(
    "Currency" character varying(255) COLLATE pg_catalog."default",
    "Currency name" character varying(255) COLLATE pg_catalog."default",
    "Currency from" character varying(255) COLLATE pg_catalog."default",
    "Scenario" character varying(255) COLLATE pg_catalog."default",
    "Fiscal year" double precision,
    "Fiscal period" character varying(255) COLLATE pg_catalog."default",
    "Currency from value" double precision,
    "Currency to value" double precision,
    "Loaddate" date
)

Your data type choices are unconventional and even arguably wrong for using double for currency.

 

I am getting no output for using:

FROM
    system."IMETA_ZTRB_MP$F_ZTBR_TA_BW2" z
WHERE
    z."Fiscal_Year" = 2024

Your table contains no matching rows.  The use of left join basically precludes any other explanation.

David J.

 

pgsql-general by date:

Previous
From: Anthony Apollis
Date:
Subject: Using a Conversion Table
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Using a Conversion Table