Replies: 2 comments 1 reply
-
Your approach is wrong.
|
Beta Was this translation helpful? Give feedback.
-
Ok, I understand your point of view. Actually in production, a part from shell user, there is no way to drop all tables. Error of mine: I forgot to precise that we need this for help in development. We have some 'fixed' data needed to be reimported, so MUST survive to db:wipe as a file dump. actually we are using mysql dump to dump files, then wiping or doing a migrate:fresh, then reimporting using mysql console command We would like to be able to intercept wipe request to act FROM CODE to force a dump of some tables. To understanda the point, these tables are html content of email templates and some fixed pages. So we must have always latest version in a file (and we will commit this until first release) We cannot use a seed to import that data from a file because the developers are actively changing the data itself and so we need to help developers be sure to not loose last versions of data they edited / received / modified |
Beta Was this translation helpful? Give feedback.
-
Whene developing, we need to intercept when db is refreshed / wiped.
I ask you kindly to add firing of a 'db_wipe' event or similar.
So we can intercept and,. for example, be sure to dump some not rebuildable data from db to file.
Beta Was this translation helpful? Give feedback.
All reactions