Best way to have database structure as per the code base.
While working on project, I have to switch on different different git branches and each branch may have a different database structure, my db size is nearly 50GB+, While running propel:install it takes a time of more than 30 min, how can I have the same db structure version as per the git branch code without wasting a time.
Answers
-
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,084 ⚖️ - Guardians (admin)
Heyhey @mitkumar.dudani.nagar ,
I think this is not a propel challenge itself: if you touch db structure in a DB which contains a lot of data it is slower than operating the same thing within a DB with much less data.
So maybe it is worth rethinking why you need such a big db for the dev environment in the first place? I see tons of downsides of having that.
What is the reason why you need such a big db all the time?
All the best,
Florian
0 -
I have to work with such amount of data, but what I have observe is after successfully running propel:install, if I run it again it is making changes to the database, ideally it should only consider the changes. But I haven't made any changes to the schema files.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 930 Developer Corner
- 788 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random