Message of the day:
Welcome. Latest release: https://www.silverstripe.org/download Community Forum: https://forum.silverstripe.org Features: https://forum.silverstripe.org/c/feature-ideas Archive: https://slackarchive.silverstripe.org
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
Archive temporarily at https://archive.codingplayground.nl (redirect)
I could build the system assuming that it will happen one day. Just make it a has_many right now. But I was hoping for a better solution
I just talked to my boss about a possible future API update...Possible being the operative word here. It may never happen.
I guess the request may change
you talk about changing has_one to has_many - and I wonder if it is better to spend a bit more time to work out what you may need more carefully
What do you mean?
but why not get has_one vs has_many right immediately?
that sounds perfect
If the relationship returns a datalist the passed in functionality would be run inside a loop. Otherwise it would be called once (in the case of a has_one)
Using callback functions or something