Loading...

XML

Word

Printable

Affects:

Release Notes
Release Note Text:

Hide
When @OrderBy was used in conjunction with a table-per-class hierarchy, the generated SQL was invalid because the "order by" clause qualified the columns using the table name instead of the alias.
The "order by" clause now qualifies the column based on the table alias, however this is limited to the table-per-class hierarchy: other column qualification strategies are still affected. For more information about other affected column qualification strategies, refer to <ulink url="https://issues.jboss.org/browse/JBPAPP-1123">~~JBPAPP-1123~~</ulink>.

Show
When @OrderBy was used in conjunction with a table-per-class hierarchy, the generated SQL was invalid because the "order by" clause qualified the columns using the table name instead of the alias. The "order by" clause now qualifies the column based on the table alias, however this is limited to the table-per-class hierarchy: other column qualification strategies are still affected. For more information about other affected column qualification strategies, refer to <ulink url=" https://issues.jboss.org/browse/JBPAPP-1123 "> JBPAPP-1123 </ulink>.
Release Note Status:
Documented as Resolved Issue
Docs QE Status:
ON_QA

is related to

JBPAPP-1123 ANN-625 - @OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax

JBPAPP-6940 HHH-4394 ManyToManyTest.testOrderByContractor fails on DB2 and Sybase

JBPAPP-7103 CLONE - ANN-625 - @OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax