public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Anthony Apollis <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Code does Not Read in FY 2025 Data
Date: Tue, 16 Jul 2024 08:39:00 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJyMCYLrTkCDwQAUWGVeE3OoH2BxJKbSZutkNtXeZALieEixOQ@mail.gmail.com>
References: <CAJyMCYJZ9xhgMyLE+U=2xAZ=DbaDb8keCb4pW5_+L4sx9brBdg@mail.gmail.com>
<[email protected]>
<CAJyMCYKdUTisoh6pBJfZPkkutqdc3Juj1BbUTeMXO5E157Secg@mail.gmail.com>
<[email protected]>
<CAJyMCYJSnh8HvWumnd18uzLtU+ZjimF+DeSaBV=uXVq8HbFEzA@mail.gmail.com>
<[email protected]>
<CAJyMCYLrTkCDwQAUWGVeE3OoH2BxJKbSZutkNtXeZALieEixOQ@mail.gmail.com>
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
[email protected]
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Code does Not Read in FY 2025 Data
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox