Fixing database "name" (=path) for SQLite#359
Closed
ThomasLandauer wants to merge 1 commit intodoctrine:3.4.xfrom
Closed
Fixing database "name" (=path) for SQLite#359ThomasLandauer wants to merge 1 commit intodoctrine:3.4.xfrom
ThomasLandauer wants to merge 1 commit intodoctrine:3.4.xfrom
Conversation
Since DBAL 3.0 (see doctrine/migrations#1028), the message currently reads for SQLite: > Careful, database "" will be purged. Do you want to continue? (yes/no) Neither @Ocramius (see doctrine/dbal#3606 (comment)) nor me (see doctrine/dbal#4982) succeeded in convincing @morozov to continue returning the file path ;-) So it looks like the fix needs to be done here... Suggestion: What about adding the platform too? So the message would be: > Careful, MySQL database "foo" will be purged. Do you want to continue? (yes/no) `doctrine/migrations` is currently broken too: > WARNING! You are about to execute a migration in database "<unnamed>" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no) [yes]: So when done here, I'm going to submit the same there (i.e. follow up of doctrine/migrations#1028)
Member
|
@ThomasLandauer please avoid mentioning people or using links to GitHub issues in commit messages. People will get spammed every time this commit is rebased or amended, and the GitHub resources will get linked to each of the rebased or otherwise amended versions. |
Contributor
Author
|
Sorry, didn't know that! So it's OK in the PR message (tab "Conversation" on GitHub's website) but not in the message when doing the actual file change (tab "Commits")? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Since DBAL 3.0 (see doctrine/migrations#1028), the message currently reads for SQLite:
Neither @Ocramius (see doctrine/dbal#3606 (comment)) nor me (see doctrine/dbal#4982) succeeded in convincing @morozov to continue returning the file path ;-) So it looks like the fix needs to be done here...
Suggestion: What about adding the platform too? So the message would be:
BTW:
doctrine/migrationsis currently broken too:So when done here, I'm going to submit the same there (i.e. follow up of doctrine/migrations#1028)