MIME-Version: 1.0
References: <CAJyMCYJZ9xhgMyLE+U=2xAZ=DbaDb8keCb4pW5_+L4sx9brBdg@mail.gmail.com>
 <1fd63ee5-a8a3-492e-a38d-82ff21da26b8@aklaver.com> <CAJyMCYKdUTisoh6pBJfZPkkutqdc3Juj1BbUTeMXO5E157Secg@mail.gmail.com>
 <82ff4dac-d8b0-4b8b-aa88-e5d74f624a4d@aklaver.com> <CAJyMCYJSnh8HvWumnd18uzLtU+ZjimF+DeSaBV=uXVq8HbFEzA@mail.gmail.com>
 <5b8cb137-121d-40c6-b907-7d59e53b5e13@aklaver.com> <CAJyMCYLrTkCDwQAUWGVeE3OoH2BxJKbSZutkNtXeZALieEixOQ@mail.gmail.com>
 <145933da-bfe0-4755-a99d-e7bde94d7416@aklaver.com>
In-Reply-To: <145933da-bfe0-4755-a99d-e7bde94d7416@aklaver.com>
From: Anthony Apollis <anthony.apollis@gmail.com>
Date: Tue, 16 Jul 2024 17:57:20 +0200
Message-ID: <CAJyMCY+Q7E7YB=YbxrLyu-B_b+y29RxtrvzR2245+wonEGvcwQ@mail.gmail.com>
Subject: Re: Code does Not Read in FY 2025 Data
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000053ea66061d5f6738"
Archived-At: <https://www.postgresql.org/message-id/CAJyMCY%2BQ7E7YB%3DYbxrLyu-B_b%2By29RxtrvzR2245%2BwonEGvcwQ%40mail.gmail.com>
Precedence: bulk

--00000000000053ea66061d5f6738
Content-Type: text/plain; charset="UTF-8"

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
>
>

--00000000000053ea66061d5f6738
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">That very same code is picking up all the data in the Orig=
inal Table. Which only contains past data.</div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 16 Jul 2024 at 17:39, Adr=
ian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@a=
klaver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">On 7/16/24 08:28, Anthony Apollis wrote:<br>
&gt; Only data up until=C2=A02024 is picked up in Revised table, whic conta=
ins <br>
&gt; 2025 data. THe Maxdate calculation seems to be the problem.<br>
<br>
This:<br>
<br>
&#39;Only data up until 2024 is picked up in Revised table, whic contains <=
br>
2025 data. ..&quot;<br>
<br>
is consistent with:<br>
<br>
MaxDate AS (<br>
=C2=A0 =C2=A0 =C2=A0SELECT<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0MAX(&quot;Date&quot;) AS &quot;MaxDate&qu=
ot;<br>
=C2=A0 =C2=A0 =C2=A0FROM<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0FullWeeks<br>
=C2=A0 =C2=A0 =C2=A0WHERE<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;Date&quot; &lt; CURRENT_DATE<br>
)<br>
<br>
I don&#39;t see how you expect to fetch data from the future when you limit=
 <br>
the data to the past.<br>
<br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div>

--00000000000053ea66061d5f6738--