Merging fails with table prefixes
| Project: | Database Scripts |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
I have had the priviledge to try dbscripts out for some days now to see if it fits with my new version control based Drupal strategy, and it does perfectly. It's a fantastic idea, and I just see one big potential in maintaining Drupal sites and distributions with dbscripts. However, after struggling to understand the concept because of some lacking documentation (which is perfectly understandable), I have a question about merging. The problem is that the merged production version doesn't preserve it's contents. When I look in the production/data/node.sql before merge I can see the nodes generated from production, but after merge the same file looks exactly the same as development/data/node.sql. Is this right? It means that content which are generated in production are wiped out.
What I've done is stepwise:
- dump.php last-merge
- Moved the content to production place, and populated database with restore.php last-merge
- Then added some content in production version and some settings config in development
- Then I dump.php production min on production and downloaded it to databases dir in development area
- Then merge.php
- Then import the changes with restore.php production min
Result: Content changes done on production are not preserved.
Is this the right steps? Or am I missing something?
Thanks!
#1
Debugging dbscripts is *really* hard. So, if you could, may you send me your config.inc, config.references.inc, and all three of your database files (you could tar them up). If you can't upload them here, you can email them to me, kathleen.murtagh AT gmail.
#2
Wow, did a clean D6 install without table prefixes and now it works much more like it should.
#3
Oh, that's really good information! So this bug is caused by #384390: Table prefixes not supported ?
If you could, save your version with the table prefixes. After I fix the issue with table prefixes, could you test it?
#4
Sure! I have different setups now prepared for testing dbscripts. I will also test some more to completely understand the complexity of dbscripts, but it is starting to look pretty amazing when it's working.
#5
We'll get back to this issue once I've fixed #384390: Table prefixes not supported