Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently if you have a wrong db_url configured (or none configured at all), the upgrade process will first do a lot of stuff and ask you 2 questions, and only then it will tell you that it fails to connect to the database.
I think it would be a good idea to do it the other way round.
Otherwise, great that this can be done with Drush! The instructions to do this manually are really scary.
Comments
Comment #1
greg.1.anderson CreditAttribution: greg.1.anderson commentedGreat suggestion; patches welcome.
Comment #2
donquixote CreditAttribution: donquixote commentedhm, let me see.. i am rewriting krumo, i want to improve the horrible crumbs admin form, i am producing a fancy meteor mobile thingie, and more stuff. help!
this is the first time i do a D6 -> D7 upgrade (honestly). Maybe on the 3rd time I would produce a patch :)
Comment #3
greg.1.anderson CreditAttribution: greg.1.anderson commentedUnderstood. Since I am very much in the same boat, #1 is also addressed to future readers, so they know that this suggestion would be welcomed if they had time to post a patch. Silence might be interpreted as disinterest.
Comment #4
colanI'm escalating this to a bug because Moshe's post says that "it is safe to run this command from within your production site" when it actually drops all tables in the source database if it's unset.
When didn't have this set initially, it must have assumed that the source was the target. It cleared up when I found the proper format for db-url over at Upgrade Drupal 6 to Drupal 7 using Drush site-upgrade.
Other folks have complained about this in Moshe's post's comments.
Here's the error that showed up in my case:
Comment #5
greg.1.anderson CreditAttribution: greg.1.anderson commentedI agree this is critical. I'll post a note on the project page.