Export db

[adrianalin89]

The GDPR prevents us from downloading any customer data so to get the faked database and not faked the live one on the server we will need an export command that will create a temporary db, clone the original db in to it, faked that db, export it and delete the temp db. Added another attribute to pick a specific place for export to go to, if not default is where the command is run. In the identify command when pressing enter it will skip the current table instead of creating it, just makes it faster than to push "n" and enter. I had cases where email was not identified correctly because it was too low in the list. When creating the config file it's a good idea to let everybody know to what package throws config files belong to. Added an auto-detection for m2 and c5 to skip writhing a long parameter list and also god for non-technical ppl Added small boilerplate for c5 db

[adrianalin89]

still need more to do but I'm curious to see what you think about my approach.

[peterjaap]

I don't understand the first part of your clarification. You state that "the GDPR prevents us from downloading any customer data". This is not actually true - if you sign a Data Processing Agreement (DPA) with the client (which you should, legally) you are totally entitled to download customer data.

Is there anything I'm missing? I'm not even sure this functionality is actually needed.

[adrianalin89]

the DPA is sign between customer and company but if the company makes outsourcing then I can't legally download the DB.

[peterjaap]

Then the outsourcing party has to sign a DPA with the customer.