MySQL temporarily modify database for development
For development I have a set of tables in a database I want to modify the tables during development and testing. But be able to go back to the original state i started with every time I run the application. is there a way to achieve this without actually backing up and restoring every time.
OS: Win10 Software: XAMPP MySQL(MariaDB) with PHP
php mysql windows-10
asked Nov 20 '18 at 8:19
DeepanDeepan
364
|
show 4 more comments
For development I have a set of tables in a database I want to modify the tables during development and testing. But be able to go back to the original state i started with every time I run the application. is there a way to achieve this without actually backing up and restoring every time.
OS: Win10 Software: XAMPP MySQL(MariaDB) with PHP
php mysql windows-10
asked Nov 20 '18 at 8:19
DeepanDeepan
364
2
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
1
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28
|
show 4 more comments
For development I have a set of tables in a database I want to modify the tables during development and testing. But be able to go back to the original state i started with every time I run the application. is there a way to achieve this without actually backing up and restoring every time.
OS: Win10 Software: XAMPP MySQL(MariaDB) with PHP
php mysql windows-10
asked Nov 20 '18 at 8:19
DeepanDeepan
364
For development I have a set of tables in a database I want to modify the tables during development and testing. But be able to go back to the original state i started with every time I run the application. is there a way to achieve this without actually backing up and restoring every time.
OS: Win10 Software: XAMPP MySQL(MariaDB) with PHP
php mysql windows-10
php mysql windows-10
asked Nov 20 '18 at 8:19
DeepanDeepan
364
asked Nov 20 '18 at 8:19
DeepanDeepan
364
asked Nov 20 '18 at 8:19
DeepanDeepan
364
asked Nov 20 '18 at 8:19
DeepanDeepan
364
asked Nov 20 '18 at 8:19
DeepanDeepan
364
364
2
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
1
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28
|
show 4 more comments
2
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
1
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28
2
2
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
1
1
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28
|
show 4 more comments
2 Answers
2
active
oldest
votes
You can make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database.
Each time you want to "go back to the start", just restore the backup (with the alternative name) again.
Backup/restore is scriptable, so you can automate it if you need to.
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
add a comment |
If your data is being exhausted as you say there's no other way than return to original state, but you might look for the ways to make it faster and easier. If the db is big and you look to shorten the restore time look at the suggestions here:
https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster
Also you can write a shell script that wraps the restore operations suggested in one of the solutions from the link above in single command.
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53388802%2fmysql-temporarily-modify-database-for-development%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database.
Each time you want to "go back to the start", just restore the backup (with the alternative name) again.
Backup/restore is scriptable, so you can automate it if you need to.
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
add a comment |
You can make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database.
Each time you want to "go back to the start", just restore the backup (with the alternative name) again.
Backup/restore is scriptable, so you can automate it if you need to.
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
add a comment |
You can make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database.
Each time you want to "go back to the start", just restore the backup (with the alternative name) again.
Backup/restore is scriptable, so you can automate it if you need to.
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
You can make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database.
Each time you want to "go back to the start", just restore the backup (with the alternative name) again.
Backup/restore is scriptable, so you can automate it if you need to.
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
answered Nov 20 '18 at 10:45
ADysonADyson
24.4k112545
24.4k112545
add a comment |
add a comment |
If your data is being exhausted as you say there's no other way than return to original state, but you might look for the ways to make it faster and easier. If the db is big and you look to shorten the restore time look at the suggestions here:
https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster
Also you can write a shell script that wraps the restore operations suggested in one of the solutions from the link above in single command.
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
add a comment |
If your data is being exhausted as you say there's no other way than return to original state, but you might look for the ways to make it faster and easier. If the db is big and you look to shorten the restore time look at the suggestions here:
https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster
Also you can write a shell script that wraps the restore operations suggested in one of the solutions from the link above in single command.
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
add a comment |
If your data is being exhausted as you say there's no other way than return to original state, but you might look for the ways to make it faster and easier. If the db is big and you look to shorten the restore time look at the suggestions here:
https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster
Also you can write a shell script that wraps the restore operations suggested in one of the solutions from the link above in single command.
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
If your data is being exhausted as you say there's no other way than return to original state, but you might look for the ways to make it faster and easier. If the db is big and you look to shorten the restore time look at the suggestions here:
https://dba.stackexchange.com/questions/83125/mysql-any-way-to-import-a-huge-32-gb-sql-dump-faster
Also you can write a shell script that wraps the restore operations suggested in one of the solutions from the link above in single command.
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
answered Nov 20 '18 at 10:27
Jarek.DJarek.D
1,0431716
1,0431716
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53388802%2fmysql-temporarily-modify-database-for-development%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
The obvious solution is not using that database for development; copy it and use the copy. Although you should probably not test with live data at all...
– jeroen
Nov 20 '18 at 8:27
Like Jeroen said, use a copy. Don't ever use your production database for testing/developing.
– Dirk Scholten
Nov 20 '18 at 8:37
Thanks, The data is just sample data. but during testing i exhaust most of the data (modified/deleted) every time. If using a copy is the right way to do it can you illustrate how to do it using MySQL or XAMPP
– Deepan
Nov 20 '18 at 10:01
1
just make a backup and then restore the backup with a different name. Then point the dev/test environment of your application (you do have a different "test" copy of your application as well, I hope?) at the new copy of the database. Each time you want to "go back to the start", just restore the backup again. Backup/restore is scriptable, so you can automate it if you need to.
– ADyson
Nov 20 '18 at 10:25
@ADyson Please answer in the answer section
– Lightness Races in Orbit
Nov 20 '18 at 10:28