RE: Masquerade Your Backups To Build QA/Testing Environments With MyDumper #1105
Replies: 2 comments 3 replies
-
Hi @matthewlenz, Yes, it has been added to the latest releases. You can use a constant value like this:
No NO NOOOO!! mydumper will continue doing
What you must do, is edit/create the -schema files for the table creation, as mydumper can't build that for you. I don't think that I will be implementing something like cols-include or cols-exclude. |
Beta Was this translation helpful? Give feedback.
-
@davidducos this makes
I tried to use |
Beta Was this translation helpful? Give feedback.
-
David, I read your blog post earlier this month and I was curious if this had been added to the most recent release? I was also curious if it is possible to use this to set a column to static value? I have a need to set a specific json column to NULL on export. Right now the way I'm doing this is dumping using --load-data and then manipulating that file directly. It would be nice to skip this step. Another reason I use --load-data is because I need to re-encrypt a specific column using a different key. The following would be super useful:
I understand that some of this functionality means that mydumper would no longer be able to just do a simple select * from ... when dumping but this would be AWESOME. Maybe that's already the case with your new masquerade functionality.
List which columns to dump.
cols-include = col1,col2,col4,col5
or
cols-exclude = col3
Allow specifying a static value.
col1
= NULLAllow application of db functions or keywords to the output of a field.
col2
= AES_ENCRYPT(AES_DECRYPT(col2
, 'myoldkeystring'), 'mynewkeystring')col2
= DEFAULTBeta Was this translation helpful? Give feedback.
All reactions