Skip to content
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

Why not xPDO? #1

Open
Mark-H opened this issue Dec 7, 2019 · 1 comment
Open

Why not xPDO? #1

Mark-H opened this issue Dec 7, 2019 · 1 comment

Comments

@Mark-H
Copy link

Mark-H commented Dec 7, 2019

I've not seen related discussion or anything about this repository, so if this was already discussed, sorry for bringing it up again.

Why implement a different ORM rather than use xPDO? The model classes, including validation and any special behavior, relations, etc.. they're already there.

@andchir
Copy link
Owner

andchir commented Dec 8, 2019

Hello Mark. Here I use the Doctrine because it is used in the API Platform (https://api-platform.com/). There is no ready-made opportunity to use another ORM. In addition, I do not like the Active Record pattern (I like the Date Mapper pattern more).
This API is automatically generated, but there is also manual work, such as setting up table relationships, hiding some data, setting access rights, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants