What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi guys I’ve a short question, maybe anyone here is willing to help. My question is related to multi
Hi guys I’ve a short question, maybe anyone here is willing to help. My question is related to multistore setup where the database schema differs for each one. Normally Spryker offers the way for programming store specific things by overriding Zed module specific for Store. Lets say I’ve a module Customer in Zed and want to extend the db schema for specific store XY. So creating a module CustomerXY and changing there the schema should work. But it behaves different and propel:diff add the column to all DBs. Any experience with something similar?
Comments
-
What happens when you run the command with the APPLICATION_STORE param? it behaves the same? Also I think you can set up different databases for different stores but the downfall is that you will need to sync them all up when working with common data
0 -
Technically it’s probably possible to have different database schema for different stores, but it’s not recommended as it complicates the system too much and could drive to unexpected behaviour.
0 -
Yes I always use APPLICATION_STORE=XY before my command: so
APPLICATION_STORE=XY docker/sdk propel:schema:copy
0 -
I know it’s not recommended. But currently I’m working on writing a migration workflow for a multistore project and I’ve the issue that migration scripts won’t be properly generated.
0 -
And the UseCase is theoretically officially supported by Spryker. So if it doesn’t work as expected I’d say it’s a bug to fix.
0 -
So anyone able to confirm that it’s a bug von the
propel:schema:copy
command, and if any issue was opened?0 -
Feel free to open support ticket at http://support.spryker.com/.
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
- 929 Developer Corner
- 787 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