I spent the whole day tracking down / debugging / updating the
org.hibernate.dialect.SQLServer2012Dialect and associated functions. I will
continue tomorrow.
On a side note SQL Server does not allow the identity column to be specified in
the insert. As such the insert SQL statements generated
I have been reviewing the change set, I see where Fabio was going. This looks
like it will address the Identify vs Sequence issue. That will still leave the
IncrediblySillyJpaMapsIdMappedIdentifierValueMarshaller not handling the
generation like the NormalMappedIdentifierValueMarshaller does.
there is a PR related to this issue (
https://github.com/hibernate/hibernate-orm/pull/3105), you can try to
verify if it solves the problem
On Tue, 21 Apr 2020 at 16:15, Jason Pyeron wrote:
> How can I help on HHH-9662 ?
>
> I have found that this fails with sequences too, when the composite
>
How can I help on HHH-9662 ?
I have found that this fails with sequences too, when the composite identifier
is another entity.
This works:
@Id
@Column(name = "registration_number")
@GeneratedValue(strategy = GenerationType.SEQUENCE)
private Long registrationNumber;
@Id
Turns out this issue may be a duplicate of a known issue, taking this over to
the dev list.
org/hibernate/test/annotations/cid/CompositeIdIdentityTest.java:
7 package org.hibernate.test.annotations.cid;
48 @RequiresDialectFeature(DialectChecks.SupportsIdentityColumns.class)
