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:26:06 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJyMCYJSnh8HvWumnd18uzLtU+ZjimF+DeSaBV=uXVq8HbFEzA@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>
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
[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