-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Consider removing all sylius_
database tables prefix
#61
Comments
👎 prefixes keep sylius logic separated from the main app logic (in the db I mean). |
I think it should be an option, not a requirement. As I said, it's can be done through Doctrine's events, giving us both options. In the current way you have just one option. |
Do you think about http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/cookbook/sql-table-prefixes.html ? |
Exactly. We can restrict the prefix only to Sylius tables, through namespace. So we can add a config option to allow prefix customization. It's a flexible and customizable solution, that allows enable/disable when desirable. sylius:
table_prefix: sylius_ |
👍 :) |
I do not see big harm in prefixes, but if we can make them optional - +1, if we make them configurable - +2! |
But I don't think we should remove them by default, I find it good practice, I clearly see what is part of custom app, and what is coming from Sylius, just like @winzou said! |
Yes, this is my intention. |
👍 |
Closable by #447 ? |
[CJMAX-55][CJMAX-56] Overriden account's address pages
Once there is no way (at least a simple way) to override the DB's tables/repositories names, I think the
sylius_
prefix should be removed. If a prefix is desirable, it can be solved using a listener that can be disabled.The text was updated successfully, but these errors were encountered: