Database created before dump import #181
Comments
|
@AlecRust How are you exporting your database? If it's not exported with |
|
Thanks for your reply @dsifford. The production site is hosted on EC2 via Bitnami, I've tried a couple ways to export the dump:
I wasn't aware of the dependency on WP-CLI. I don't think it's available in the current environment, will investigate. |
|
It also fails when importing a dump created via WP-CLI: Click to expand!
|
|
Can you try MariaDB and see if there's a difference? Just curious. |
|
Sadly same errors/end result as previous WP-CLI dump attempt, when using MariaDB: Click to expand!I wasn't actually aware I could just in theory swap |
|
This is definitely odd because I use this project on almost a daily basis and import a database without any issues. Also the rest of the folks on my team use this without problems. The reason why I am hesitant to change this is because in the case of the partial database export, some of the required tables may or may not be there (example: if you only export your posts table, you'll be missing your options, users, etc tables). I can't see any reason why your setup would be any different than mine. |
|
I think you might just be dumping your database incorrectly. This is a screenshot of what a piece of my resultant exported db looks like...
As you can see... It drops and recreates the table. |
|
Yeah it's strange, as I've used wordpress-starter with success in the past (beats MAMP hands down!). The export command I'm running is simply My dump also has the Separate from the issues with tables not being overwritten correctly it seems the |
|
Can you try setting your |
|
@dsifford that was it thank you! 🎉 dump now imports with no significant errors and final database works great. Click to expand!Not sure why it doesn't work with just I notice env var |
Recently pushed up a php8 image which is now the default Re: overridden env vars. That shouldn't happen. Nothing in this project writes to those. They are just read from. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Starting wordpress-starter from an existing database dump, a database is created before the dump starts, causing errors in the import and quite a broken end result.
macOS 11.3.1
docker version20.10.6
docker-compose.ymlProject structure
docker-compose upoutputClick to expand!
Problem Details
As you can see from this part of the logs, it seems a new database is first created, and then the database import starts, which fails to update important tables such as
wp_optionsas the tables already exist.Shouldn't the import only use the database dump as the database, instead of first creating a database?
This is from a clean Docker install on a new machine. The
docker-compose.ymlis copied over from when this was previously working on my old machine (with an oldervisiblevc/wordpressimage.The text was updated successfully, but these errors were encountered: