-
Notifications
You must be signed in to change notification settings - Fork 3
[NO TICKET] Fix_database_cmd_warnings #331
Open
Ioannis
wants to merge
2
commits into
COmanage:develop
Choose a base branch
from
Ioannis:Fix_database_cmd_warnings
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+137
−11
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we try getting these issues addressed upstream rather than having to patch around DBAL behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benno Before we can begin implementing changes, I believe it is essential to first upgrade to the latest version, which is currently 4.3. Once the system is up to date, we can start evaluating and suggesting modifications. For instance, introducing changes such as
ALTER INDEX IF EXISTS
should be considered early in the process. However, our initial priority should be to complete the version upgrade.After upgrading, I would like to reassess these changes. This will allow us to determine whether the latest upstream code addresses our concerns or if any issues remain. The goal of this pull request is twofold: first, to resolve any issues or warnings reported at runtime via the command line, which can be confusing for deployers; and second, to address deprecations in preparation for the upgrade.
As part of the 5.2.7 upgrade, I have updated DBAL to the latest 3.x release for stability. Once we are running the most recent version of CakePHP, we can safely move to the latest DBAL and begin making further improvements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benno i created the CFM-467 ticket to track the reassessment