| From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
|---|---|
| To: | Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Destination Table - Condition Amount 0 |
| Date: | 2024-08-08 18:48:32 |
| Message-ID: | 59275D17-8C36-4297-AD02-46B515ED3D0F@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 8 Aug 2024, at 20:07, Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com> wrote:
>
> The same code bring in values for FY24, 23 etc. Dont understand why FY25's values are 0.
If you use the same code for FY24, then either there’s some filter being applied somewhere that excludes FY25 (and probably beyond), or something in your data changed. My bet is on the latter.
For example, in FY25 the value of NCD_EXCL."Order Quantity" is 'NCD Valid FY25’, which doesn’t match your LIKE expression. Even something like a trailing space to the value could be enough.
Alban Hertroys
--
There is always an exception to always.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2024-08-08 18:55:22 | Re: Column type modification in big tables |
| Previous Message | Lok P | 2024-08-08 18:38:39 | Re: Column type modification in big tables |