You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
8a94345a7a
1.0.x
1.1.x
2.0.x
2.1.x
2.2.x
2.3.x
2.4.x
3.0.x
3.1.x
3.2.x
3.3.x
3.4.x
3.5.x
4.0.x
gh-pages
issue/1828-aggregate-ref-with-convertable
issue/1929-upgrade-hsql
issue/1935-jdbc-sql-type-for-null
issue/1953
issue/2059-query-derivation-custom-converter
issue/2138-query-with-pageable
issue/2199
issue/year-as-integer
main
1.0.0.M1
1.0.0.M2
1.0.0.M3
1.0.0.RC1
1.0.0.RC2
1.0.0.RELEASE
1.0.1.RELEASE
1.0.10.RELEASE
1.0.11.RELEASE
1.0.12.RELEASE
1.0.13.RELEASE
1.0.14.RELEASE
1.0.15.RELEASE
1.0.16.RELEASE
1.0.17.RELEASE
1.0.18.RELEASE
1.0.19.RELEASE
1.0.2.RELEASE
1.0.20.RELEASE
1.0.21.RELEASE
1.0.3.RELEASE
1.0.4.RELEASE
1.0.5.RELEASE
1.0.6.RELEASE
1.0.7.RELEASE
1.0.8.RELEASE
1.0.9.RELEASE
1.1.0.M1
1.1.0.M2
1.1.0.M3
1.1.0.M4
1.1.0.RC1
1.1.0.RC2
1.1.0.RC3
1.1.0.RELEASE
1.1.1.RELEASE
1.1.10.RELEASE
1.1.11.RELEASE
1.1.12.RELEASE
1.1.13.RELEASE
1.1.2.RELEASE
1.1.3.RELEASE
1.1.4.RELEASE
1.1.5.RELEASE
1.1.6.RELEASE
1.1.7.RELEASE
1.1.8.RELEASE
1.1.9.RELEASE
2.0.0.M1
2.0.0.M2
2.0.0.M3
2.0.0.M4
2.0.0.RC1
2.0.0.RC2
2.0.0.RELEASE
2.0.1.RELEASE
2.0.2.RELEASE
2.0.3.RELEASE
2.0.4.RELEASE
2.0.5.RELEASE
2.0.6.RELEASE
2.0.7.RELEASE
2.0.8.RELEASE
2.0.9.RELEASE
2.1.0
2.1.0-M1
2.1.0-M2
2.1.0-RC1
2.1.0-RC2
2.1.1
2.1.10
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.2.0
2.2.0-M1
2.2.0-M2
2.2.0-M3
2.2.0-M4
2.2.0-M5
2.2.0-RC1
2.2.1
2.2.10
2.2.11
2.2.12
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.3.0
2.3.0-M1
2.3.0-M2
2.3.0-M3
2.3.0-RC1
2.3.1
2.3.10
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.4.0
2.4.0-M1
2.4.0-M2
2.4.0-M3
2.4.0-M4
2.4.0-RC1
2.4.1
2.4.10
2.4.11
2.4.12
2.4.13
2.4.14
2.4.15
2.4.16
2.4.17
2.4.18
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8
2.4.9
3.0.0
3.0.0-M1
3.0.0-M2
3.0.0-M3
3.0.0-M4
3.0.0-M5
3.0.0-M6
3.0.0-RC1
3.0.0-RC2
3.0.1
3.0.10
3.0.11
3.0.12
3.0.2
3.0.3
3.0.4
3.0.5
3.0.6
3.0.7
3.0.8
3.0.9
3.1.0
3.1.0-M1
3.1.0-M2
3.1.0-M3
3.1.0-RC1
3.1.1
3.1.10
3.1.11
3.1.12
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
3.2.0
3.2.0-M1
3.2.0-M2
3.2.0-M3
3.2.0-RC1
3.2.1
3.2.10
3.2.11
3.2.12
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
3.3.0
3.3.0-M1
3.3.0-M2
3.3.0-RC1
3.3.1
3.3.10
3.3.11
3.3.12
3.3.13
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
3.3.9
3.4.0
3.4.0-M1
3.4.0-RC1
3.4.1
3.4.10
3.4.11
3.4.12
3.4.13
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.5.0
3.5.0-M1
3.5.0-M2
3.5.0-RC1
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
4.0.0
4.0.0-M1
4.0.0-M2
4.0.0-M3
4.0.0-M4
4.0.0-M5
4.0.0-M6
4.0.0-RC1
4.0.0-RC2
4.0.1
${ noResults }
Jens Schauder
8a94345a7a
When the child of a one-to-one relationship has an id, the value for that id gets read in the wrong way. We get the column name for that id use that to access the value in the RowDocument. This results in either no value at all being found or even worse, the value of a root entity with a property of same name being accessed. This is fixed by using the full AggregatePath instead of just the property for accessing that value. Closes #1684 Original pull request: #1775 |
2 years ago | |
|---|---|---|
| .. | ||
| main | Fix access of root property instead of child property. | 2 years ago |
| test | Fix access of root property instead of child property. | 2 years ago |