Or, if you have *explicit* expectations you could, you know, explicitly
define them :)
On Fri, Aug 21, 2015 at 10:30 AM Steve Ebersole wrote:
> Well you can do that. Thats just not historically how Hibernate worked.
>
> Set `prefer_sequence_per_entity` to true
>
> On Fri, Aug 21, 2015 at 10:26
Well you can do that. Thats just not historically how Hibernate worked.
Set `prefer_sequence_per_entity` to true
On Fri, Aug 21, 2015 at 10:26 AM Sanne Grinovero
wrote:
> Ok, thanks and sorry I missed this :)
> I was aware that it would switch to sequences rather than identity,
> but I missed
Ok, thanks and sorry I missed this :)
I was aware that it would switch to sequences rather than identity,
but I missed that there would be a single Sequence shared among
types... I still find that a bit surprising as I would expect to
generally want different sequences for each type.
Thanks,
Sanne
Please see the migration guide and/or blogs :)
Yes, we changed the default mapping for how id generators are mapped as
discussed extensively on the mail list last month or earlier this month.
Essentially we changed the default for
`hibernate.id.new_generator_mappings` from false to true for 5.0.
Hi all,
after upgrading Hibernate Search to Hibernate ORM 5.0.0.Final we
noticed a small change in behaviour in sequences.
In a single test we persist two entities of differnent types, Country
and Address, and both types have the id mapped as follows:
@Id
@GeneratedValue
Long id;
Previo