Timeline for Importing minor DB changes from local to live server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2018 at 12:10 | comment | added | Christoph Farnleitner | I see, this is a slightly different topic than I did assume then. However, I would not dare to step down from my point saying that you just shouldn't touch the database directly. But, did you consider creating an XML-based export for your module by looping through all data you want to share with the other database? At the live env you than could populate the database again using a data script. | |
| Feb 10, 2018 at 1:01 | comment | added | MployBy | @ChristophFarnleitner, we have set-up scripts for our extensions. All default settings are auto set/new tables after created. I am talking about transferring user populated data. For example you installed event module and on test server, website owner created 500 events (to save time and not do that on live) - how would you transfer them to live? Set-up script will create table for this module on live server, but not transfer 500 events that were created by owner on test server. | |
| Feb 10, 2018 at 0:17 | answer | added | Steven J | timeline score: 0 | |
| Feb 9, 2018 at 21:08 | comment | added | Christoph Farnleitner | Actually, you shouldn't - at all - be doing what you seem to do. Modifying the database structure (creating or altering tables or columns) is a task for a setup scripts. Populating fields or tables with initial/updated data is a task for data scripts. See also inchoo.net/magento/… | |
| Feb 9, 2018 at 20:39 | history | asked | MployBy | CC BY-SA 3.0 |