Hi Jurgen,
thanks for the suggestions :). I made a horrible hack just now, based on the
idea of having a different model, but instead of modifying files, I remove the
relationships in memory. This actually works but it would be interesting to
hear the point of view of others—am I potentially
Hi Hugi
So crazy idea number one is to maybe duplicate your model and revise the
delete rules, then use this DeleteModel to nuke the customer. The downside
of this is having to maintain two models, maybe not such a good idea ?
Idea number two is to add a delete method to each of the classes
I'm a fan of well-named things ... deleteWithoutMercy and
horribleMutantRuntimeWithoutRelationships are fabulous!
On Thu, May 30, 2019 at 6:44 AM Hugi Thordarson wrote:
> Hi Jurgen,
>
> thanks for the suggestions :). I made a horrible hack just now, based on
> the idea of having a different
Fortunately for the programming world, I'm currently mainly in the business of
consuming APIs rather than designing them :p
> On 30 May 2019, at 14:01, Michael Gentry wrote:
>
> I'm a fan of well-named things ... deleteWithoutMercy and
> horribleMutantRuntimeWithoutRelationships are fabulous!
