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 #7491] Switching from MySQL to PostgreSQL and vice versa doesn't change the port in the resource configuration #1084

Closed
icinga-migration opened this issue Oct 29, 2014 · 12 comments
Labels
area/configuration Affects the configuration bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by elippmann on 2014-10-29 15:06:36 +00:00

Assignee: jmeyer
Status: Resolved (closed on 2015-04-07 13:07:55 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-04-07 13:07:55 +00:00 (in Redmine)


As a user, I do not want to set the default port for MySQL and PostgreSQL when switching the database type because I may not know what the default port is.

Changesets

2015-04-07 13:07:36 +00:00 by jmeyer dc4d124

Fix that the sql port does not change when updating the type of the database

fixes #7491

Relations:

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-11-05 08:40:56 +00:00

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

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-11-05 10:26:32 +00:00

  • Status changed from Assigned to New
  • Assigned to deleted jmeyer

This is difficult to implement with our refactored form implementation. Form::createElements(), which does the entire decide-which-default-values-to-use-on-autosubmit job, is not able to prevent submitted values from being populated.

There is some work to be done in the base Form before this issue can be solved. :(

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-11-21 11:09:50 +00:00

  • Duplicated set to 7779

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-11-21 11:13:05 +00:00

  • Relates set to 7717

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-11-21 11:13:57 +00:00

I've added #7717 as related issue because its fix might apply here as well.

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-11-21 15:39:17 +00:00

  • Target Version changed from 2.0-16 to Backlog

@icinga-migration
Copy link
Author

Updated by jmeyer on 2015-02-05 07:24:42 +00:00

  • Duplicated set to 8361

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-27 15:04:51 +00:00

  • Target Version changed from Backlog to 2.0.0-rc1

@icinga-migration
Copy link
Author

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

  • Tracker changed from Feature to Bug
  • Subject changed from Resource Configuration: Switching from MySQL to PostgreSQL and vice versa must change the port to Switching from MySQL to PostgreSQL and vice versa doesn't change the port in the resource configuration

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-04-02 08:34:40 +00:00

  • Relates set to 8958

@icinga-migration
Copy link
Author

Updated by jmeyer on 2015-04-07 08:41:46 +00:00

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

@icinga-migration
Copy link
Author

Updated by jmeyer on 2015-04-07 13:07:56 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset dc4d124.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/configuration Affects the configuration bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant