Re: Code does Not Read in FY 2025 Data - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Code does Not Read in FY 2025 Data
Date
Msg-id 5b8cb137-121d-40c6-b907-7d59e53b5e13@aklaver.com
Whole thread Raw
In response to Code does Not Read in FY 2025 Data  (Anthony Apollis <anthony.apollis@gmail.com>)
Responses Re: Code does Not Read in FY 2025 Data
List pgsql-general
On 7/16/24 08:15, Anthony Apollis wrote:

Reply to list also
Ccing list

> i did attached the sample data.

Yes I know and the data for 2025  will fail because they are like this:

Date FY    Period    Quarter    Day    Month    Year    Loaddate
2025-01-10 00:00:00.000    NULL    NULL    NULL    10    1    2025    2023-07-10 11:55:09.733

The FY values are NULL and they will not be found by:

"FY" IS NOT NULL AND "FY" >= 'FY24'

For the updated data that is for 2026 and 2027 there are FY values, but 
then you do:

WEEK_NUMBER."Date" < CURRENT_DATE

where WEEK_NUMBER is the alias for the sub-select that filtered on:

"FY" IS NOT NULL AND "FY" >= 'FY24'

So even if the sub-select found values in the future you filter them out 
  with < CURRENT_DATE

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Code does Not Read in FY 2025 Data
Next
From: Adrian Klaver
Date:
Subject: Re: Code does Not Read in FY 2025 Data