Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Invalid SQL produced when using FetchMode.SUBSELECT with SQLServerDialect

Description

For example, enabling org.hibernate.test.subselect.CompositeIdTypeBindingTest for SQL-Server by removing the corresponding annotation @SkipForDialect and running the matrix-test on an SQL-Server would produce the following exception.

This is due to execution of this SQL-statement which is invalid for SQL-Server:

Attachments

1

Activity

Show:

Benjamin Runnels October 27, 2017 at 2:06 PM

I can confirm this is still happening in Hibernate 5.2.10.Final

Tobias Brueggemann April 7, 2016 at 10:35 AM
Edited

After applying the attached patch-file the test will pass. The SQL-statement (for SQL-Server only) then looks like:

The attached patch-file also introduces a new test-case org.hibernate.test.subselectfetch.compositeid.SubselectFetchCompositeIdTest derived from org.hibernate.test.subselectfetch.SubselectFetchTest and a test-case org.hibernate.test.subselectfetch.multilevel.MultiLevelTest that would fail on SQL-Server without applying the patch.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created April 7, 2016 at 10:34 AM
Updated October 27, 2017 at 7:51 PM
Configure