Re: Code does Not Read in FY 2025 Data

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Code does Not Read in FY 2025 Data
Date: 2024-07-16 15:39:00
Message-ID: 145933da-bfe0-4755-a99d-e7bde94d7416@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message pradeep t 2024-07-16 15:49:07 Re: Semantic cache capability for Postgresql db
Previous Message Anthony Apollis 2024-07-16 15:34:58 Re: Code does Not Read in FY 2025 Data