Create the possibility that entities from a xif (external db) are read-only somehow

On our radar

you can set "normal" entities read-only in an espace so you can control the consistency of the data in the espace itself (expose them with actions etc.)

however, you cannot do the same thing with external-xif-entities.

what I like to see you could achieve the same as with "normal" entities.
set them read-only and create actions to CUD them in a designated espace.
Perhaps you can assign a designated espace to it which is allowed to do anything.
and the other espaces only can read those entities in queries.

hope I made myself a bit clear :)

Created on 10 Jul 2012
Comments (3)
I understand what you're getting at, and indeed the problem would be the scope of the read-only, as the CRUD actions can't reside in the extension itself.
Merged this idea with 'Entity in Integration enhancement - readonly and dedicated wrapper-espace' (created on 2015-05-27 08:15:10 by J.)

Since we can set "normal" entities to read-only, I would like to see that in my extension as well.

With the exception that I can assign an espace to be able to use the CRUD-actions to wrap it.
I can do this no matter what, but to prevent other espaces to use the generated CRUD-actions is a pain.
This wil also help to create wrappers for entities with a multi-PK

Merged from 'Entity in Integration enhancement - readonly and dedicated wrapper-espace' (idea created on 2015-05-27 08:15:10 by J.), on 2017-07-21 06:10:11 by J.