1:51 p.m.
We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails if null
is passed to Session.evict()
The application passes null since the code is generic.
Are there any alternatives?
Thanks,
Amit.
3:37 p.m.
This list is for discussions about the development of Hibernate, not for
usage discussions.
The behavior you describe sounds the most reasonable to me actually, tbh.
Also, generic code can (should, I'd argue) still do null checks...
On Thu, May 8, 2014 at 6:51 AM, amit shah <amits.84(a)gmail.com> wrote:
We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails
if null
is passed to Session.evict()
The application passes null since the code is generic.
Are there any alternatives?
Thanks,
Amit.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
7:01 a.m.
Ok. I will move this discussion to the users group.
I understand that it sounds reasonable to have a null check but the
important point is that it has broken backwards compatibility. Any thoughts
on that?
On Thu, May 8, 2014 at 7:07 PM, Steve Ebersole <steve(a)hibernate.org> wrote:
This list is for discussions about the development of Hibernate, not
for
usage discussions.
The behavior you describe sounds the most reasonable to me actually, tbh.
Also, generic code can (should, I'd argue) still do null checks...
On Thu, May 8, 2014 at 6:51 AM, amit shah <amits.84(a)gmail.com> wrote:
> We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails if
> null
> is passed to Session.evict()
> The application passes null since the code is generic.
>
> Are there any alternatives?
>
> Thanks,
> Amit.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
1:37 p.m.
Here's the thing about "backwards compatibility"... That's only true
if
the behavior is documented and/or tested as such or if the behavior is just
"inherently reasonable".
As you even seem agree, the previous behavior is not inherently reasonable;
its at best questionable. So then can you point me to some documentation
or regression tests that assert evict should accept nulls?
On Fri, May 9, 2014 at 12:01 AM, amit shah <amits.84(a)gmail.com> wrote:
Ok. I will move this discussion to the users group.
I understand that it sounds reasonable to have a null check but the
important point is that it has broken backwards compatibility. Any thoughts
on that?
On Thu, May 8, 2014 at 7:07 PM, Steve Ebersole <steve(a)hibernate.org>wrote:
> This list is for discussions about the development of Hibernate, not for
> usage discussions.
>
> The behavior you describe sounds the most reasonable to me actually, tbh.
> Also, generic code can (should, I'd argue) still do null checks...
>
>
> On Thu, May 8, 2014 at 6:51 AM, amit shah <amits.84(a)gmail.com> wrote:
>
>> We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails if
>> null
>> is passed to Session.evict()
>> The application passes null since the code is generic.
>>
>> Are there any alternatives?
>>
>> Thanks,
>> Amit.
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>
3891
days inactive
3892
days old
3 comments
2 participants
participants (2)
-
amit shah -
Steve Ebersole