Well to be fair, I already reported that this "regression" was
introduced in 4.2.8 by placing the ON predicate on the target table join
instead of the collection table join as was done before in 4.2.7.SP1.
I am not using 4.x anymore but since Wildfly ships with Hibernate 5.0, I
suppose that othe
It is so... :)
On Thu, Sep 22, 2016, 3:11 PM Gail Badner wrote:
> +1
>
> On Thu, Sep 22, 2016 at 6:30 AM, andrea boriero
> wrote:
>
>> +1
>>
>> On 22 September 2016 at 14:18, Steve Ebersole
>> wrote:
>>
>> > I propose that we limit who has the ability to create issues in the
>> > Hibernate Jir
+1
On Thu, Sep 22, 2016 at 6:30 AM, andrea boriero
wrote:
> +1
>
> On 22 September 2016 at 14:18, Steve Ebersole wrote:
>
> > I propose that we limit who has the ability to create issues in the
> > Hibernate Jira JPA project.
> >
> > Users routinely create issues there incorrectly, rather than
Hi Christian,
We are only backporting critical issues and regressions to 5.0 at this
point, so it can't be backported to 5.0. If no regressions caused by this
fix are reported in 5.2, I would consider backporting to 5.1.
Regards,
Gail
On Wed, Sep 21, 2016 at 12:14 AM, Christian Beikov <
christia
+1
On 22 September 2016 at 14:18, Steve Ebersole wrote:
> I propose that we limit who has the ability to create issues in the
> Hibernate Jira JPA project.
>
> Users routinely create issues there incorrectly, rather than the ORM (HHH)
> project.
> ___
I propose that we limit who has the ability to create issues in the
Hibernate Jira JPA project.
Users routinely create issues there incorrectly, rather than the ORM (HHH)
project.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists
Well therein lies (yet another) minor rub
On Thu, Sep 22, 2016 at 7:06 AM Steve Ebersole wrote:
> Well therein lies a minor rub in having split SQM out from ORM.
> Specifically if the "compliance violation" occurs in the HQL/JPQL/Criteria
> query the exception is a type from SQM (it has no d
Well therein lies a minor rub in having split SQM out from ORM.
Specifically if the "compliance violation" occurs in the HQL/JPQL/Criteria
query the exception is a type from SQM (it has no deps on ORM). Here
though it is not reasonable to throw an SQM exception type.
On Wed, Sep 21, 2016 at 2:
