-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
db:import | flag to not initialize Magento #890
Comments
I have problems to reproduce what you describe, for me it just works (see below for a log), I exported a dump, removed all tables from the database und imported the dump with Please provide more details about the concrete problem you've been running into, e.g. the concrete command and it's output.
|
@tkn98 during your test you're using the |
Ah, okay, well it would be convenient to create the db then as we can read the db name from the Magento configuration. Also we could add a create database if not exists to the dump output, I think that is an option for mysqldump we use to create the dumps. Perhaps both wouldn't hurt. However having the create database within the dump.sql file would tight the dump to the database name. |
Just not it get's lost: When we provide parameters to override configuration database infos (host:port, db, credentials, socket etc.) we should consider having these parameters as well for the |
When setting up a new environment with an existing database dump, we want to use n98-magerun db:import to import the dump. But at that point, the database is empty so Magento cannot be initialized and the dump cannot be imported. A nice feature would be something like
--no-initialize
to just do an import, maybe querying database credentials from the user instead of reading them from the Magento configuration (or reading app/etc/local.xml beforehand).The text was updated successfully, but these errors were encountered: