| From: | Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(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:57:20 |
| Message-ID: | CAJyMCY+Q7E7YB=YbxrLyu-B_b+y29RxtrvzR2245+wonEGvcwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-07-16 16:05:29 | Re: Code does Not Read in FY 2025 Data |
| Previous Message | pradeep t | 2024-07-16 15:49:07 | Re: Semantic cache capability for Postgresql db |