On Fri, Oct 24, 2014 at 4:30 PM, Steve Ebersole wrote:
> As for 4.3.x, for me that again goes back to this not being a bug. 4.3 is a
> maintenance branch now, meaning it should only include bug fixes in any
> releases. So IMO this should not be part of the 4.3 branch. I do want to
> have a disc
I personally do not think it is correct to change the existing behavior
here, but I do not have a strong feeling for it. I just believe that you
don't change historical behaviors that work as designed except as protected
by the setting to enable the new feature or improvement.
I really do not get
Hi Steve,
On Fri, Oct 24, 2014 at 3:08 PM, Steve Ebersole wrote:
> As to your specific question, yes I think what you propose makes sense.
> Namely, if this setting is enabled, I think it is reasonable to treat a null
> component reference and an empty component reference as equivalent.
Thanks f
Hi Guillaume,
In general, yes, there is interest in this. I think quite a few folks have
asked for it, so certainly it would be nice to make it an option. We've
all just been busy lately.
As to your specific question, yes I think what you propose makes sense.
Namely, if this setting is enabled,
Hi!
Any interest in us pursuing this?
We are obviously committed to update the documentation once we have
validated it's the way to go.
Thanks for your feedback.
On Tue, Oct 14, 2014 at 3:23 PM, Guillaume Smet
wrote:
> Hi all,
>
> So, after a long time without any issue (rest assured we were b
Hi all,
So, after a long time without any issue (rest assured we were busy
anyway!), we got around a new problem we would like to fix in ORM:
HHH-7610 .
It's a long standing complaint about the embedded and the fact that
empty components are returned from the ORM.
We had the "good" idea to fix i
