-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name Examination: Consider timezone when updating NR expiration date #18524
Comments
@iamjtodd i am bumping the priority up to 1 on this one, because its related to an ops ticket and related to this ticket here: urgent ticket 17475. please let me know if you want to discuss |
I don't know how to check NR in COLIN... But I can provide you the data in Oracle db after updating NR expiration date. Let me know if I can be help. |
Deployed to test environment and ready to test |
Comments related to this ticket have been updated on #18301 |
There is an issue encountered when updating the expiry date of an existing NR. During synchronization with Oracle, the date in the PostgreSQL "namex" database is copied to the Oracle "namesp" database without undergoing any conversion to the local time. As a consequence, the expiry date in the Oracle database is one day ahead of the expected value.
A modernization developer will need to change the code that updates existing expiry dates as follows:
select expiration_date at time zone 'America/Vancouver' from requests
More details please reference to
#17475
The text was updated successfully, but these errors were encountered: