Skip to content
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

[dev.icinga.com #9027] PostgreSQL schema sets default timestamps w/o time zone #2884

Closed
icinga-migration opened this issue Apr 9, 2015 · 6 comments
Labels
area/db-ido Database output bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9027

Created by elippmann on 2015-04-09 08:23:55 +00:00

Assignee: elippmann
Status: Resolved (closed on 2015-05-04 14:02:43 +00:00)
Target Version: 2.4.0
Last Update: 2015-05-04 14:03:13 +00:00 (in Redmine)

Icinga Version: v2.3.0-82-gdda273d
Backport?: No
Include in Changelog: 1

The timestamp columns in the PostgreSQL schema are defined as timestamp with time zone but their default values lack the UTC time zone offset +00. Thus default timestamps are converted to local time in the zone specified by PostgreSQL's configuration before being displayed to the client.

Changesets

2015-04-09 08:31:20 +00:00 by elippmann 8414d40

Fix PostgreSQL schema not specifying the time zone for default timestamps

The timestamp columns in the PostgreSQL schema are defined as timestamp with time zone but their default values lack the time zone offset +00.
Thus default timestamps are converted to local time in the zone specified by PostgreSQL's configuration before being displayed to the client.

refs #9027

2015-04-09 08:31:58 +00:00 by elippmann e4f6bcb

Add PostgreSQL schema upgrade to IDO version 1.14.0 for adding the time zone for default timestamps

refs #9027

2015-04-09 08:32:56 +00:00 by elippmann 0925c80

Add yet empty MySQL schema upgrade to IDO version 1.14.0

refs #9027

2015-05-04 09:35:41 +00:00 by elippmann 6a77d99

Fix PostgreSQL schema not specifying the time zone for default timestamps

The timestamp columns in the PostgreSQL schema are defined as timestamp with time zone but their default values lack the time zone offset +00.
Thus default timestamps are converted to local time in the zone specified by PostgreSQL's configuration before being displayed to the client.

refs #9027

2015-05-04 09:35:41 +00:00 by elippmann fe3eba8

Add PostgreSQL schema upgrade to IDO version 1.14.0 for adding the time zone for default timestamps

refs #9027

2015-05-04 09:35:41 +00:00 by elippmann 1e0df43

Add yet empty MySQL schema upgrade to IDO version 1.14.0

refs #9027

2015-05-04 09:35:41 +00:00 by (unknown) 0c0f53b

Fix schema version 1.14.0

refs #9027

2015-06-17 14:11:21 +00:00 by (unknown) f6c5f58

Fix wrong timestamp w/ timezone format in DB IDO PGSQL schema

refs #9027

Relations:

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-04-09 08:26:34 +00:00

  • Subject changed from PostgreSQL schema sets default timestamps w/o timezone to PostgreSQL schema sets default timestamps w/o time zone

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-12 13:19:28 +00:00

  • Target Version set to 2.4.0

I need to figure out which 1.x schema version this should be, but most likely 1.14.0 is sufficient considering a 2.4.0 release in November, or so

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-12 13:20:50 +00:00

  • Copied To set to 9047

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-05-01 10:56:09 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

I'm thinking about releasing 1.13.3 rather soon-ish. We might consider adding the schema change to 2.3.5 as well as it will affect the Icinga Web 2 release later this year (and 2.4.0 is definitely too late for that).

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-05-04 14:02:43 +00:00

  • Status changed from Assigned to Resolved
  • Assigned to changed from mfriedrich to elippmann
  • Done % changed from 0 to 100
  • Estimated Hours set to 2

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-05-04 14:03:13 +00:00

  • Backport? changed from TBD to No

Will happen with 1.14.0 and 2.4.0, no backports.

@icinga-migration icinga-migration added bug Something isn't working area/db-ido Database output labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.4.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/db-ido Database output bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant