Skip to content

Request to modify postgres model to use timezone-aware timestampz #871

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

Closed
spring-projects-issues opened this issue Jul 7, 2018 · 2 comments
Labels
in: core related-to: ddl-scripts status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details type: enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

Gary P Russo opened BATCH-2734 and commented

To avoid any dependency or conflicts with the client time zone, it is considered a best practice to use Postgres TIMESTAMPZ instead of TIMESTAMP.

The postgres table creation script is currently using the TIMESTAMP data type. 

https://github.com/spring-projects/spring-batch/blob/master/spring-batch-core/src/main/resources/org/springframework/batch/core/schema-postgresql.sql

 


Affects: 4.0.1

Reference URL: http://www.postgresqltutorial.com/postgresql-timestamp/

@fmbenhassine fmbenhassine removed the status: waiting-for-triage Issues that we did not analyse yet label Mar 23, 2021
@fmbenhassine fmbenhassine added this to the 5.0.0 milestone Mar 23, 2021
@fmbenhassine fmbenhassine modified the milestones: 5.0.0, 5.0.0-M6 Aug 31, 2022
@fmbenhassine fmbenhassine modified the milestones: 5.0.0-M6, 5.0.0-M7 Sep 21, 2022
@fmbenhassine fmbenhassine modified the milestones: 5.0.0-M7, 5.0.0-M8 Oct 4, 2022
@fmbenhassine fmbenhassine changed the title Request to modify postgres model to use timezone-aware timestampz [BATCH-2734] Request to modify postgres model to use timezone-aware timestampz Oct 11, 2022
@fmbenhassine
Copy link
Contributor

FTR, an attempt was made to implement this in #4209. Due to the issues that popped up in that attempt, this feature is delayed to a future version.

@fmbenhassine fmbenhassine removed this from the 5.0.0-M8 milestone Oct 11, 2022
@fmbenhassine
Copy link
Contributor

Closing this for the reasons explained in #4209.

@fmbenhassine fmbenhassine closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2025
@fmbenhassine fmbenhassine added the status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details label Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core related-to: ddl-scripts status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants