Remove PHPCR layer completely, or at least make it optional #7305
Jurek-Raben
started this conversation in
Ideas
Replies: 2 comments
-
A few years ago there was talk of replacing PHPCR: "we’ll be replacing our current content storage solution, PHPCR, with our own content storage tool". But it has not happened (yet) and I don't think it was mentioned publicly again. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, in Sulu 3 PHPCR is going to be replaced with the Sulu Content Bundle which is based on JSON. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sulu is a great cms with a lot of benefits, and also currently the only headless cms which runs symfony 6.4.
It uses a PHPCR standard to store any content data... But this standard does not seem to be very handy at all, and the benefit seems to be questionable, too. Also this decision comes with a bunch of disadvantages:
So my suggestion would be to make this whole layer optional, and instead use a human readable, most simple database relation structure, which can be easily queried, manipulated from outside and performs well. Maybe there is a common standard for these structures, too, I don't know. Common are a tree table, a category/page table, and content table. Where i18n is required, it should use a join table, to have no redundacy.
Replacing PHPCR and all XML configuration. Instead using lightweight structures like JSON.
Beta Was this translation helpful? Give feedback.
All reactions