Would love to see the option to mark an entity as being a singleton, meaning: max one object of this entity can exist.
Very useful for instance for an entity called ‘Configuration’.
This could get added below ‘Persistable’
Related, but not the same is Andrej’ idea: https://community.mendix.com/link/ideas/2221
Shouldn't a singleton pattern assert, that there is exactly one instance?
What is your expected behaviour?
* should the platform handle the creation of the instance?
* how should standard retrieves behave - is a retrieve list still possible/meaningfull?
* should the platform prevent creation at runtime? Or even not allow to use create actions during development?
I also find the idea quite interesting, but it's not easy to pinpoint a good approach.
Maybe a java action like 'GetSingleton(Entity)' that handles a bit of this would already serve a good job.
Would love to see that feature. Even though singletons are a anti pattern it would help a lot ensuring theres always 1 config at any time. Any chance getting this feature in the future?