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

From Anthony Apollis
Subject Re: Code does Not Read in FY 2025 Data
Date
Msg-id CAJyMCY+Q7E7YB=YbxrLyu-B_b+y29RxtrvzR2245+wonEGvcwQ@mail.gmail.com
Whole thread Raw
In response to Re: Code does Not Read in FY 2025 Data  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Code does Not Read in FY 2025 Data
List pgsql-general
That very same code is picking up all the data in the Original Table. Which only contains past data.

On Tue, 16 Jul 2024 at 17:39, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 7/16/24 08:28, Anthony Apollis wrote:
> Only data up until 2024 is picked up in Revised table, whic contains
> 2025 data. THe Maxdate calculation seems to be the problem.

This:

'Only data up until 2024 is picked up in Revised table, whic contains
2025 data. .."

is consistent with:

MaxDate AS (
     SELECT
         MAX("Date") AS "MaxDate"
     FROM
         FullWeeks
     WHERE
         "Date" < CURRENT_DATE
)

I don't see how you expect to fetch data from the future when you limit
the data to the past.


--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: pradeep t
Date:
Subject: Re: Semantic cache capability for Postgresql db
Next
From: Adrian Klaver
Date:
Subject: Re: Code does Not Read in FY 2025 Data