Re: Using a Conversion Table

2024-02-15 Thread Peter J. Holzer
On 2024-02-14 10:02:37 -0500, Greg Sabino Mullane wrote: >     "Fiscal year" double precision, > > This column is an INTEGER in your other table, so your schema is not even > internally consistent! Try to use TEXT, INT, DATE and TIMESTAMPTZ whenever > possible, While using double precision fo

Re: Using a Conversion Table

2024-02-14 Thread Greg Sabino Mullane
> > "Fiscal year" double precision, > This column is an INTEGER in your other table, so your schema is not even internally consistent! Try to use TEXT, INT, DATE and TIMESTAMPTZ whenever possible, with NUMERIC as needed for things with a precision. See: https://www.postgresql.org/docs/current

Re: Using a Conversion Table

2024-02-14 Thread David G. Johnston
On Wednesday, February 14, 2024, Anthony Apollis 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."defau

Using a Conversion Table

2024-02-14 Thread Anthony Apollis
*I am trying to convert a column from ZAR Column " Amount_in_Company_Code_Currency" " to USD.* Table: CREATE TABLE IF NOT EXISTS system."IMETA_ZTRB_MP$F_ZTBR_TA_BW2" ( "Company_Code" character varying(255) COLLATE pg_catalog."default", "Posting_Period" integer, "Fiscal_Year" integer,