>> > major release being developed, and the matter of possible time
>> > pressure.
>> >
>>
>> Thus the proposal of Yoann and me to just rename the current 6 to a later
>> version and release a new major version that only contains the Jakarta
>&g
Thus the proposal of Yoann and me to just rename the current 6 to a later
> version and release a new major version that only contains the Jakarta
> package change.
>
> That way, we don't end up doing additional work and having weird versions
> partially supporting both.
>
>
ting both.
--
Guillaume
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
but it will break all existing
> > applications in a minor, not ideal
> > - move 6 to jakarta packages too to avoid conflicts
> >
> > 2/
> > - rename 6 to 7 (or 8)
> > - release a 6 (or 7) with jakarta packages
> >
> > I don't think tying the Jakar
se to the 6 cycle is a good
> idea so that's not an option for me.
>
> Note that in any case, some patches will be significantly harder to
> backport to 5.4 (and vice versa).
>
> --
> Guillaume
> _______
> hibernate-dev mailing list
>
kage release to the 6 cycle is a good
idea so that's not an option for me.
Note that in any case, some patches will be significantly harder to
backport to 5.4 (and vice versa).
--
Guillaume
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
http
ting to
> >>> explore a partial migration, for example I suppose it might be
> >>> possible for us to "accept" the use of mapping annotations from JPA
> >>> 3.0 (on top of the ones from JPA 2.0) while not exposing the full
> >>> proper API yet.
>
API is literally the same contract, if you except the
>>> package name, it might be feasible to expose the full JPA 3.0 in a
>>> backwards compatible way as well but this might require:
>>>- use of bridge methods, e.g. bytecode manipulation at build time [1]
>>>- d
(for example)
> > Hibernate ORM 5.5.x were to depend on both JPA 2 and JPA 3 API
> > artifacts?
> >
> > And additional change to take into account is that the JPA3 API now
> > defines a module-info resource; it would be nice to try taking
> > advantage of
ge to take into account is that the JPA3 API now
> defines a module-info resource; it would be nice to try taking
> advantage of that but it's of course more complicated if we have a
> hybrid JPA 2/3 implementation. I guess that aspect will have to wait
> for ORM6, but also that OR
g the JPA3 groundwork.
Thanks,
Sanne
1 - https://github.com/dmlloyd/bridger
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
/f8b78bcad0df43bd9b69fa5ee9d3bf10a3202318
>>> [2] https://hibernate.atlassian.net/browse/HHH-11838
>>> [3]
>>>
>>> https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/proxy/pojo/ProxyFactoryHelper.java#L87-L94
>>> _______
>>> hibernate-dev mailing list
>>> hibernate-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
https://hibernate.atlassian.net/browse/HHH-11838
>> [3]
>>
>> https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/proxy/pojo/ProxyFactoryHelper.java#L87-L94
>> ____
eate an HHH jira and create a pull request.
>> >
>> > Thanks,
>> > Gail
>> >
>> > [1]
>> >
>> https://github.com/gbadner/hibernate-core/commit/2d368a2ce1da36468ab7f965467711bc59f439cf
>> > _______
&g
I will
> > create an HHH jira and create a pull request.
> >
> > Thanks,
> > Gail
> >
> > [1]
> >
> https://github.com/gbadner/hibernate-core/commit/2d368a2ce1da36468ab7f965467711bc59f439cf
> > _______
]
>
> https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/proxy/pojo/ProxyFactoryHelper.java#L87-L94
> _______
> hibernate-dev mailing list
> hibernate-d
/commit/2d368a2ce1da36468ab7f965467711bc59f439cf
> ___________
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
know if this is a reasonable improvement. If it is, I will
create an HHH jira and create a pull request.
Thanks,
Gail
[1]
https://github.com/gbadner/hibernate-core/commit/2d368a2ce1da36468ab7f965467711bc59f439cf
___
hibernate-dev mailing list
hibernate-dev
/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/proxy/pojo/ProxyFactoryHelper.java#L87-L94
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
WildFly application?
>>
>> Any plans to enable that?
>>
>> Thanks,
>>
>> --Gunnar
>> _______
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
ut
> Quarkus, e.g. within a WildFly application?
>
> Any plans to enable that?
>
> Thanks,
>
> --Gunnar
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://l
Hi,
An interesting question came up during the Quarkus meet-up with Harald
Pehl here in Hamburg last night: could Panache also be used without
Quarkus, e.g. within a WildFly application?
Any plans to enable that?
Thanks,
--Gunnar
___
hibernate-dev
://github.com/orgs/eclipse-vertx/projects/1
Andy has been contributing on Quarkus as well: don't hesitate to reach
out to him for any need, as I hope he'll be able to help on RX too.
Thanks,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
8.4, Elasticsearch 7.6 and Hibernate ORM
5.4.12.Final.
For more information, see our blog:
https://in.relation.to/2020/02/24/hibernate-search-6-0-0-Beta5/
Yoann Rodière
Hibernate Team
yo...@hibernate.org
___
hibernate-dev mailing list
hibernate-dev
nfigured with
> Maven 3.6. Jobs configured with Maven 3.5 or below will be affected by the
> bug.
>
> Cheers,
>
> Yoann Rodière
> Hibernate Team
> yo...@hibernate.org
> ___
> hibernate-dev maili
.
The CI already uses Maven 3.6.3 by default for all jobs configured with
Maven 3.6. Jobs configured with Maven 3.5 or below will be affected by the
bug.
Cheers,
Yoann Rodière
Hibernate Team
yo...@hibernate.org
___
hibernate-dev mailing list
hibernate
SE users having a
flat classloader and just needing to run some quick in-memory tests on
H2.
Thanks
>
> >> Here again, the ask is so we can educate and point people to use
> >> statelessSession rather than dropping Hibernate fully and from that
> >> api if needed go d
o this quickly:
> - https://hibernate.atlassian.net/browse/HHH-13861
>
> Andrea volunteered to have a look; assigned to him assuming it's
> straight forward; if it gets tricky we'll have to wait for Steve's
> opinion.
>
that one is now fixed and that’s awesome. one less deprecation I'm
forced to use :)
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
://in.relation.to/2020/02/19/hibernate-search-5-11-5-Final-and-5-10-9-Final/
Cheers,
Yoann Rodière
Hibernate Team
yo...@hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
t into:
>> >> >INFO [org.hib.Version] HHH000412: Hibernate ORM core version
>> >> > 5.4.11-SNAPSHOT
>> >> >
>> >> > in particular:
>> >> > - to remove the "{}" wrapping around the number
>> >> > - add "ORM"
>>
4.11-SNAPSHOT
> >> >
> >> > in particular:
> >> > - to remove the "{}" wrapping around the number
> >> > - add "ORM"
> >> > - lowercase "core" and add "version"
> >> >
> >> > Looks good? It w
This was an urgent bugfix release, but we managed to include some
enhancements as well!
Please check out the blog post:
https://in.relation.to/2020/02/14/hibernate-orm-5-4-12/
Thanks,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Please do not push anything to master branch.
Thanks,
Andrea
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
] HHH000412: Hibernate ORM core version
>> > 5.4.11-SNAPSHOT
>> >
>> > in particular:
>> > - to remove the "{}" wrapping around the number
>> > - add "ORM"
>> > - lowercase "core" and add "version"
t
> api if needed go do `.doWork()` rather than refer to deprecated
> `.connection()`
Makes sense, I believe we should be able to do this quickly:
- https://hibernate.atlassian.net/browse/HHH-13861
Andrea volunteered to have a look; assigned to him assuming it's
straight forward; if it gets tricky we'll have to wait for Steve's
opinion.
Thanks!
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
rojects/jdk/14/#Schedule
[2] https://openjdk.java.net/jeps/3
[3] https://openjdk.java.net/jeps/3#Fix-Request-Process
[4]
https://mail.openjdk.java.net/pipermail/jdk-dev/2020-February/003885.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
_______
eRegistry standardRegistry = new
StandardServiceRegistryBuilder().applySettings(settings).build();
MetadataSources sources = new MetadataSources(standardRegistry);
sources.add{Class|Package|Jar}(...);
//etc.
SessionFactory sessionFactory =
sources.getMetadataBuilder().build().getSessionFactoryBui
sion the alternative is `doWork`. Any reason why that api isn't
> available on stateless session ?
>
> Here again, the ask is so we can educate and point people to use
> statelessSession rather than dropping Hibernate fully and from that
> api if needed go do `.doWork()` rather than refer to deprecated
> `.connection()`
>
>
Makes sense
Dave Cramer
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
api if needed go do `.doWork()` rather than refer to deprecated
`.connection()`
Thanks,
/max
https://xam.dk/about
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi all,
we have released Hibernate ORM 5.4.11.Final !
For details:
https://in.relation.to/2020/02/07/hibernate-orm-5411-final-release/
Thanks all!!
Andrea
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman
ot;core" and add "version"
> >
> > Looks good? It would be more consistent with our own project
> > naming/branding, and with the format of similar messages being logged
> > by other popular libr
Please do not push anything to master branch.
Thanks,
Andrea
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
; and add "version"
>
> Looks good? It would be more consistent with our own project
> naming/branding, and with the format of similar messages being logged
> by other popular libraries.
>
> Thanks,
> Sanne
> ___
> hibern
other popular libraries.
Thanks,
Sanne
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
-search-6-0-0-Beta4/
Yoann Rodière
Hibernate Team
yo...@hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
It was actually released 07/Jan/2020. Apologies for the late announcement!
https://in.relation.to/2020/01/23/hibernate-orm-5315-final-out/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
here:
https://in.relation.to/2020/01/23/hibernate-validator-6-1-1-released/ .
Have a nice day.
--
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
020-January/005274.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
private Employee employee;
> ...
> }
>
> In this particular case, the foreign keys have been deleted, so it's
> possible to load and delete these entities.
>
> An attempt to insert an entity on either side results in:
> org.hibernate.PropertyValueException: not-null property
xception: cyclic dependency in derived identities
Please let me know...
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org<mailto:hibernate-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
__
ts in:
org.hibernate.PropertyValueException: not-null property references a null
or transient value
When converted to use @MapsId and @JoinColumns instead, Hibernate throws:
org.hibernate.MappingException: cyclic dependency in derived identities
Please let me know...
Thanks,
Gail
____
t; `#setObject` methods (`#getObject` as well?). Does the driver handle
>>> this.
>>> >
>>> > Out of curiosity, which jdbc driver are you helping with?
>>> >
>>> >
>>> >
>>> > On Thu, Jan 9, 2020 at 10:23 AM Dave Cramer
>&
t;> >
>> >
>> >
>> > On Thu, Jan 9, 2020 at 10:23 AM Dave Cramer
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> As one of the maintainers of the postgres jdbc driver I am interested
>> in
>> >> this disc
gres jdbc driver I am interested in
> >> this discussion.
> >> Postgres only stores date/times in UTC. Everything else is a
> translation.
> >> The driver uses the client's timezone for all dates/times (for better or
> >> worse) If there is anything I can do to
se is a translation.
>> The driver uses the client's timezone for all dates/times (for better or
>> worse) If there is anything I can do to help make things easier, let me
>> know.
>>
>>
>>
>> --
>> Sent from: http://hibernate-development.74578.x6.nabbl
know.
>
>
>
> --
> Sent from: http://hibernate-development.74578.x6.nabble.com/
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
_____
If I ask Java to parse
>>> "2020-01-01 10:10:10 America/Chicago +02:00" it just says no. For me, CST
>>> (standard) and CDT (daylight savings) are really synonyms for offset -
>>> either UTC-05:00 or UTC-06:00 depending on day of the year.
>>>
&
easier, let me
know.
--
Sent from: http://hibernate-development.74578.x6.nabble.com/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
kPachot/postgresql-bind-variable-peeking-fb4be4942252
>
> [3]
>
> https://blog.jooq.org/2018/04/12/why-sql-bind-variables-are-important-for-performance/
>
> [4]
>
> https://blog.jooq.org/2017/05/30/when-to-use-bind-values-and-when-to-use-inline-values-in-sql/
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
t; https://medium.com/@FranckPachot/postgresql-bind-variable-peeking-fb4be4942252
>
> [3]
> https://blog.jooq.org/2018/04/12/why-sql-bind-variables-are-important-for-performance/
>
> [4]
> https://blog.jooq.org/2017/05/30/when-to-use-bind-values-and-when-to-use-inline-values-in-sql/
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
when-to-use-bind-values-and-when-to-use-inline-values-in-sql/
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
o disagree that query literals should always be rendered as
SQL literals.
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
ase optimizer can build a "better" plan
> using a literal versus a parameter is generally pretty small. I
> can think of partition columns, tenancy columns - things of that
> nature. You think its more broad?
>
If the selectivity estimates for a parameter are low, and in bi
m such injection attacks.
2. The cases where the database optimizer can build a "better" plan
using a literal versus a parameter is generally pretty small. I can think
of partition columns, tenancy columns - things of that nature. You
think its more broad?
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
think that is
> enough. Conceptually that is what "JDBC time zone" is supposed to mean
> exactly what we are discussing here, right?
>
Right
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
what "JDBC time zone" is supposed to mean
exactly what we are discussing here, right?
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
uot;parsing it" and (2) applying it to SQL. Different parts
> of
> > > the puzzle.
> > >
> > > Yep.
> > >
> > > Yoann Rodière
> > > Hibernate Team
> > > yo...@hibernate.org
> > >
> > >
> > > On T
ain, this topic is about HQL parsing.
Yes, handling temporal values at the JDBC/SQL level can be very tricky.
That's true however whether that temporal value is an HQL literal or an
attribute value.
And its just a completely different topic overall.
>
___________
2020 at 19:50, Steve Ebersole <mailto:st...@hibernate.org>> wrote:
> >
> > > As far as I know, even Java does not support that. A true
> zone-id would
> > >> be something like (for me) "America/Chicago". If I ask Java
> to parse
&
true zone-id
> would
> > >> be something like (for me) "America/Chicago". If I ask Java to parse
> > >> "2020-01-01 10:10:10 America/Chicago +02:00" it just says no. For me,
> > CST
> > >> (stand
CST
> >> (standard) and CDT (daylight savings) are really synonyms for offset -
> >> either UTC-05:00 or UTC-06:00 depending on day of the year.
> >>
> >
> > It seems like the proper syntax for that would actually be "2020-0
cago", but in my
> testing DateTimeFormatter#parseBest did not handle that form either
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Formatter#parseBest did not handle that form either
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
support for various temporal-related things such as how to
>> handle formatting (to_char, etc), extraction and temporal arithmetic -
>> specifically formalizing and normalizing them across databases.
>>
>
> Nice. As long as it uses org.hibernate.type.Type implementations when i
izing and normalizing them across databases.
>
Nice. As long as it uses org.hibernate.type.Type implementations when it
comes to converting between Java values and SQL values, it should be safe.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
o_char, etc), extraction and temporal arithmetic -
specifically formalizing and normalizing them across databases.
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
s or suggestions regarding any of this?
>
>
> [1] -
>
> https://github.com/hibernate/hibernate-orm/blob/eab6107ec2e7b3a0c06146a9ff51b9964f4b3169/hibernate-core/src/main/antlr/org/hibernate/grammars/hql/HqlParser.g4#L484
> _______
> hibernate
ate-core/src/main/antlr/org/hibernate/grammars/hql/HqlParser.g4#L484
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[1]
https://mail.openjdk.java.net/pipermail/jdk-dev/2019-December/003795.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
t; >>>
>>>> >>>> We have been trying to keep a balance of maintainable code base for
>>>> >>>> Hibernate vs legacy/counter intuitive/plain wrong DB designs. The
>>>> answer is
>>>> &
gt;> >>>>
>>> >>>> As an example you might Imagine someone wants to put
>>> >>>> internationalization properties into a database and having a table
>>> >>>> structure like this (this might be an old legacy application that
>>> doesn't
>>> >>>&g
ALE as , as in this case the systems
>> >>>> default locale would be used, but for each BUNDLE_NAME/KEY
>> combination you
>> >>>> could only have a single composite key with a LOCALE.
>> >>>>
>> >>>> Hibernate should be (must be?) able to handle this scenario,
in his role as Developer Advocate
at Google Cloud Platform, and a Java Champion too.
Also if you don't mind, advertise it on twitter:
- https://twitter.com/Hibernate/status/1207321287623954432
Thanks,
Sanne
___
hibernate-dev mailing list
hibernate-dev
nate allows null to
> be
> >>>>> a valid id value. Because null means I don't know or not applicable.
> >>>>> I think in the past we argued the same for attributes of a composite
> >>>>> id,
> >>>>> like you s
gt;>>> Emmanuel
>>>>>
>>>>> On 11 Dec 2019, at 3:37, Gail Badner wrote:
>>>>>
>>>>>> Currently, there is no way to load an entity that exists in the
>>>>>> database
>>>>>> with a composite ID, if one of the composite ID columns is null.
>>>>&g
ibernate/type/ComponentType.java#L671-L675
>>>> >
>>>> > Basically, if any field/property in a composite ID is null, Hibernate
>>>> > assumes the entire ID is null. An entity cannot have a null ID, so it
>>>> > returns null for the entity result.
>>>> >
>>>> > I believ
, Elasticsearch 7.5 and Hibernate
ORM 5.4.10.Final.
For more information, see our blog:
https://in.relation.to/2019/12/16/hibernate-search-6-0-0-Beta3/
Yoann Rodière
Hibernate Team
yo...@hibernate.org
___
hibernate-dev mailing list
hibernate-dev
v/2019-December/003795.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hibernate does allow a primary key column to be
>>> > nullable.
>>> >
>>> > TBH, it seems strange to have a property in a composite ID that can be
>>> > null. If it can be null, it seems that the property could be removed
>>> > from
>>> > the composite key.
>>> >
&g
-L675
>>>>
>>>> Basically, if any field/property in a composite ID is null,
>>>> Hibernate
>>>> assumes the entire ID is null. An entity cannot have a null ID, so
>>>> it
>>>> returns null for the entity result.
>>>>
does allow a primary key column to be
>> > nullable.
>> >
>> > TBH, it seems strange to have a property in a composite ID that can be
>> > null. If it can be null, it seems that the property could be removed
>> > from
>> > the composite key.
&g
a primary key column to be
>>> nullable.
>>>
>>> TBH, it seems strange to have a property in a composite ID that can
>>> be
>>> null. If it can be null, it seems that the property could be removed
>>> from
>>> the composite key.
>>
gt; > fields/properties must be non-null. Am I missing something?
> >
> > The code I referenced above is 13 years old. Does anyone have insight
> > into
> > why Hibernate does this?
> >
> > Thanks,
> > Gail
> > _____
see anything in the spec about a requirement that all
> composite ID
> fields/properties must be non-null. Am I missing something?
>
> The code I referenced above is 13 years old. Does anyone have insight
> into
> why Hibernate does this?
>
> Thanks,
> Gail
>
referenced above is 13 years old. Does anyone have insight into
why Hibernate does this?
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
gt;>> properties have been detected, and throw an exception if this is not the
>>> case.
>>>
>>> 2) A class used as an IdClass does not need any annotations (as opposed
>>> to
>>> a class used for an EmbeddedId class, which requires {{@Embeddable}}).
superclass would need to be annotated with
>> {{@MappedSuperclass}} in order for its fields/properties to be persistent.
>> Since the field/property names must match what is annotated in an IdClass,
>> it is clear that the field/property in a superclass is intended to be an
>> ID. Perhaps we could make annotating the superclass with
>> {{@MappedSuperclass}} optional?
>>
>> Opinions?
>>
>> Thanks,
>> Gail
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
lass,
> it is clear that the field/property in a superclass is intended to be an
> ID. Perhaps we could make annotating the superclass with
> {{@MappedSuperclass}} optional?
>
> Opinions?
>
> Thanks,
> Gail
> _______
> hibernate-de
t is clear that the field/property in a superclass is intended to be an
ID. Perhaps we could make annotating the superclass with
{{@MappedSuperclass}} optional?
Opinions?
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists
,
> ...
> };
> assert idValues.length %2 == 0;
> session.get( EntityWithCompositeId.class, idValues );
>
> Of course, if the embedded-id could also have an id-class you'd use that.
>
> I'd like to see all of these as options btw, not one-or-the-other.
> Though I'm fine if no-one else likes the `Session#byCompositeId` idea.
> It was just a spur-of-the-moment idea.
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
501 - 600 of 15471 matches
Mail list logo
