The JPA spec is completely silent on inheritance when it comes to
embeddable classes. When Emmanuel was first developing
hibernate-annotations we decided to allow the use of @MappedSuperclass to
be extended to embeddable classes to control the persistence of attributes
when an embeddable had a sup
Not really. In general any token whose text is explicitly given in any of
the grammars will be treated as a keyword. Generally speaking this is
merely an oversight when someone alters the grammars. However, the
definition of the OBJECT token actually hasn't changed since the SVN
migration. The
As of 4.2.12, there are some identifiers that no longer work when used in
HQL/JPQL, e.g. [1].
Is there a list of reserved words somewhere?
Thanks,
Gail
[1] https://hibernate.atlassian.net/browse/HHH-9154
___
hibernate-dev mailing list
hibernate-dev@li
On 12 Jan 2014, at 18:15, Emmanuel Bernard wrote:
> I am not sure I understand everything you said.
Same here.
> how about you take 20 mins tomorrow during our Hibernate NoORM team meeting
> on IRC?
> Be careful, 20 mins run fast in practice :)
+1 That meeting is at 16:00, right? Need to se
I am not sure I understand everything you said. how about you take 20 mins
tomorrow during our Hibernate NoORM team meeting on IRC?
Be careful, 20 mins run fast in practice :)
On 12 May 2014, at 17:38, Sanne Grinovero wrote:
> Now that finally Infinispan moved to build (and require) Java7, I'm
Now that finally Infinispan moved to build (and require) Java7, I'm
preparing to upgrade the Lucene Directory to Apache Lucene 4.8.
Sometimes it's trivial, some others we're out of luck and this is one
of such situations: the new Lucene code expects some new methods to
create and validate a CRC32
