Skip to content
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 dump development; exclude all, except like 2 #950

Open
seansan opened this issue Oct 6, 2017 · 3 comments
Open

db dump development; exclude all, except like 2 #950

seansan opened this issue Oct 6, 2017 · 3 comments

Comments

@seansan
Copy link

seansan commented Oct 6, 2017

We use db dump development, no payments, orders, customers, etc anonymous

But sometimes we really really need 1 or 2 examples created on LIVE

How can we use db dump development for example, but retain 2 customers, 2 orders and their payments, shippings etc

So strip all: except maybe 2

Maybe an idea

@ktomk
Copy link
Collaborator

ktomk commented Oct 6, 2017

This is not really feasible with the routines we have. This sounds a bit like a fixture for a test-system (in the general sense this could be your development system for example). For Magento 1 there is a test-framework which has fixture support (e.g. EcomDev_PHPUnit or with less fixture support maybe Digital Pianism Test Framework), with that you can at least automate creation of sample customers (also possible with Magerun) but also orders etc..

@seansan
Copy link
Author

seansan commented Oct 6, 2017 via email

@cmuench
Copy link
Member

cmuench commented Oct 6, 2017

I have no idea how we can do this. Most data have dependencies that why we only have a hard “export" or "skip" data. Filtering on datasets is not easy with export tools like mydqldump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants