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
One hack I have found is to add, inside the subprojects block of
the build.gradle file, the following task
task copyResourcesToIntelliJOutFolder(type: Copy) {
from "$subProject.buildDir/resources/test"
into 'out/test/resources'
}
Then in the IntelliJ gradle tool window locate the
section on the series page. For example: http://hibernate.org/
> search/releases/5.8/#whats-new. Obviously you'll want to keep yours
> shorter, I'm just not good at summarizing ;)
>
> Thanks,
>
> Yoann Rodière
> Hibernate NoORM Team
> yo...@hibernate.org
>
>
Thanks a lot Guillaume and Yoann, great work.
On 28 September 2017 at 17:41, Steve Ebersole wrote:
> To be honest, I think that is perfect process Guillaume. I can now define
> all that content and information in one place, which is a huge win. Which
> make me think of a
Thanks Guillame
the *orm/releases//index.adoc* file should be changed only in case
of a major or minor not for a micro, am I right?
On 28 September 2017 at 16:58, Chris Cranford wrote:
> Thanks Guillaume.
>
> On 09/28/2017 10:25 AM, Guillaume Smet wrote:
> > Hi ORM guys,
I think the new layout is fine except for the gold background colour of the
project names, I really do not like it.
What about an opinion from the jboss.org design team?
On 26 September 2017 at 17:08, Guillaume Smet
wrote:
> On Tue, Sep 26, 2017 at 3:47 PM, Davide
I think it would be a good idea to post on Google+ whenever we add a new
blog article
On 28 September 2017 at 12:26, Sanne Grinovero wrote:
> On 28 September 2017 at 11:11, Yoann Rodiere wrote:
> > +1. Either we properly mirror our tweets/blog posts to
I think so too.
On 14 August 2017 at 15:50, Vlad Mihalcea wrote:
> I guess we should create the nested embeddable as well.
>
> Vlad
>
> On Fri, Aug 11, 2017 at 2:02 AM, Gail Badner wrote:
>
> > If an embeddable contains an embeddable, and the outer
it looks really good to me, the only little doubt is related with the
example in the "how Hibernate is useful" Performance subsection, the
example looks to me more appropriate for the "Developer time" subsection.
On 4 August 2017 at 21:09, Vlad Mihalcea wrote:
> Hi
+1 for removing it
On 27 July 2017 at 10:54, Vlad Mihalcea wrote:
> If we make this change, we need to make sure the StoredProcedureQuery works
> properly for functions too:
>
> https://vladmihalcea.com/2016/04/27/how-to-call-sql-server-
>
hi Sanne,
what about sfi.getMetamodel().entityPersister( x ).getClassMetadata(); ?
On 7 July 2017 at 12:55, Sanne Grinovero wrote:
> Hi all,
>
> Hibernate Search is using this method, but it's deprecated with the
> following comment:
> "Use the descriptors from
Hi Ashudeep,
The changes are part of a series of changes introduced by
https://github.com/dreab8/hibernate-orm/commit/9caca0ce37d5a2763d476c6fa2471addcca710ca
Basically the logic related with the identifier case strategy (upper, lower
or mixed) to use is managed by
I think your consideration makes sense.
Trying to remember the reasons driving my choice to use the empty String
instead of null for the getTables method, but at the moment nothing that
pops us in my mind prevents the use of null.
On 4 July 2017 at 09:15, Ashudeep Sharma
In my opinion deprecating something is useful only when we are able to
provide an alternative, not sure about the best approach in case we do not
have a current alternative.
On 28 June 2017 at 08:55, Vlad Mihalcea wrote:
> I would use the regular Java deprecation
Hi Margot,
thanks for the feedback.
5.1.4 introduced a new default strategy used to retrieve JDBC Metadata that
requires the the default_schema to be provided.
In order to obtain the previous behaviour the
hibernate.hbm2ddl.jdbc_metadata_extraction_strategy
can be set to 'individually'.
I
I lean to your 3th option
On 3 May 2017 at 15:01, Steve Ebersole wrote:
> To circle back to this... I mentioned possibly keeping a reference to the
> foreign-key defining the join predicate between the root table and the
> secondary table. ATM however we do not model FKs
No objection
On 28 Apr 2017 17:51, "Steve Ebersole" wrote:
> Currently Hibernate implements the JPA metamodel contracts with a series of
> wrapper objects defined in the `org.hibernate.metamodel` package. This is
> non-ideal because it is a wrapper approach rather than
the proposal, names and structure, looks good to me.
I would just change, in the SecondaryTableBinding, the attribute name
"predicate" to "foreignKey"
On 14 April 2017 at 18:24, Steve Ebersole wrote:
> Before I get deeper into this persister work I wanted to discuss some
For details:
http://in.relation.to/2017/04/14/hibernate-orm-5210-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
+1 for removing the Serializable restriction
On 27 March 2017 at 18:37, Steve Ebersole wrote:
> In all versions of Hibernate to-date we have required that the Java type of
> an id be Serializable. Strictly speaking JPA has no such restriction - it
> says ids can be any
I do not have a strong opinion about it, but I'm leaning towards defining
this as an SPI
On 22 March 2017 at 18:15, Steve Ebersole wrote:
> Coming back to this to see if people see this as an API concern, of if we
> should define this as an SPI.
>
> One potential argument
For details:
http://in.relation.to/2017/03/16/hibernate-orm-529-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
For details:
http://in.relation.to/2017/02/17/hibernate-orm-528-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
Vlad, it would be great to add this info to the documentation.
On 13 February 2017 at 12:59, Steve Ebersole wrote:
> It is designed to work that way.
>
> On Mon, Feb 13, 2017 at 1:43 AM Vlad Mihalcea
> wrote:
>
> > Hi,
> >
> > I got the following
And naturally a separate jira :)
On 7 Feb 2017 13:30, andrea boriero <and...@hibernate.org> wrote:
> It's better to have a separate.
>
> On 7 Feb 2017 13:17, "Mark Rotteveel" <m...@lawinegevaar.nl> wrote:
>
> On 7-2-2017 14:12, Vlad Mihalcea wrote:
>
Hi Mark,
I think it's better to have a separate PR.
Thanks
On 7 Feb 2017 13:17, "Mark Rotteveel" wrote:
On 7-2-2017 14:12, Vlad Mihalcea wrote:
> +1.
>
> I forgot to mention to add a Jira issue. If you don't have time, let me
> know, and I'll take care of this issue for
+1 for MariaDB dialect.
+1 also for the deprecated repos
On 6 February 2017 at 15:05, Vlad Mihalcea wrote:
> I'll create a new Jira issue for the MariaDB Dialects.
>
> For the deprecated Dialects, I'd just remove them. But the Javassist
> support can be moved to a to
after thinking a bit on +1 for Steve proposal
On 31 January 2017 at 08:09, Gunnar Morling wrote:
> Agreed, it'd be the right time if we wanted to change this.
>
> I vote for 1 in case we do it.
>
> In ORM it's enough for many use cases to just add that core module,
> hence
Not have a strong opinion on the renaming.
On 30 Jan 2017 19:05, "andrea boriero" <and...@hibernate.org> wrote:
I worked on the ORM relocation script probably a year ago, I'll have to go
back and refresh my memory. Tomorrow I'll give a look at it.
On 30 Jan 2017 16:44, &quo
I worked on the ORM relocation script probably a year ago, I'll have to go
back and refresh my memory. Tomorrow I'll give a look at it.
On 30 Jan 2017 16:44, "Steve Ebersole" wrote:
> Relatedly, I have been thinking whether we want to rename the ORM artifacts
> as well
+1 to remove
On 28 Jan 2017 20:44, "Chris Cranford" wrote:
> +1 to remove as well
>
>
> On 01/27/2017 01:50 PM, Sanne Grinovero wrote:
> > +1 to remove
> >
> > On 27 January 2017 at 18:34, Vlad Mihalcea
> wrote:
> >> I'm for removing it even if it
trying to find a valid reason to keep UserType but not able, so I'm for
removing it.
On 23 January 2017 at 14:36, Vlad Mihalcea wrote:
> Hi,
>
> I see no reason why we should keep it indefinitely. I'd say we deprecate it
> in 5.x, and remove it later (6.0 or 6.1).
>
For details:
http://in.relation.to/2017/01/19/hibernate-orm-527-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
I agree with Steve and Gunnar.
On 16 January 2017 at 15:41, Gunnar Morling wrote:
> +1 The source JARs are the important thing here.
>
> Just tried out the JavaDoc view in Eclipse for the first time as
> you're mentioning it. Can't say I find it overly useful nor that I've
+1 for removing createFilter()
On 3 January 2017 at 15:54, Gunnar Morling wrote:
> 2017-01-03 15:28 GMT+01:00 Steve Ebersole :
>
> > On Tue, Jan 3, 2017 at 5:31 AM Gunnar Morling
> > wrote:
> >
> >> 2017-01-02 15:27 GMT+01:00
I think it should return the Columns
that reports the physical Table for its Table.
On 20 Dec 2016 22:02, "Steve Ebersole" wrote:
Christian provided some good feedback on the HipChat channel and we have
started a discussion about those there.
I have run into a new one
For details:
http://in.relation.to/2016/12/20/hibernate-orm-526-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
For details:
http://in.relation.to/2016/11/24/hibernate-orm-525-final-release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
For details:
http://in.relation.to/2016/10/26/hibernate-orm-524-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
I think attempting to dynamically infer what to do using the existing ctr
would be great
On 24 October 2016 at 21:49, Steve Ebersole wrote:
> I'm not sure what you are getting at. This is a feature Hibernate has had
> for close to 15 years. It's not a "new feature", I'm
I'm inclined towards the second option but not sure if it can have
limitations compared to the first one.
On 5 October 2016 at 22:59, Steve Ebersole wrote:
> In SQM's domain metamodel we decided to follow JPA's guidelines in terms
> of javax.persistence.metamodel.Metamodel.
For details:
http://in.relation.to/2016/10/03/hibernate-orm-523-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
+1 for always disallowing
On 30 September 2016 at 17:02, Steve Ebersole wrote:
> The JPA spec specifically says:
>
>
> Either positional or named parameters may be used. Positional and named
> parameters must not be mixed in a single query.
>
>
> I was thinking about how
reading the jira comments I think yes we should.
On 30 September 2016 at 15:11, Steve Ebersole wrote:
> TLDR: Should we adjust to allow Dialect to know the "context" of where the
> remapping is requested?
>
> Ah Oracle...
>
> So this comes from the fact that Oracle does not
Due to troubles with my Nexus account the release is not yet completed
anyway It's now possible to push to master.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
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
+1
On 22 September 2016 at 14:18, Steve Ebersole wrote:
> I propose that we limit who has the ability to create issues in the
> Hibernate Jira JPA project.
>
> Users routinely create issues there incorrectly, rather than the ORM (HHH)
> project.
>
Hi Petar,
you can use Identifier#toIdentifier(String text)
this method detects if the text is quoted and it calls
the Identifier#toIdentifier( String text , boolean quoted ) with the
correct quoted value.
On 21 September 2016 at 16:54, Petar Tahchiev wrote:
> Hey
+1
On 21 Sep 2016 02:00, "Steve Ebersole" wrote:
> In the interest of questioning everything, just to make sure we are all on
> the same page, Hibernate's support for native SQL queries currently
> recognizes named parameters, positional parameters as well as JDBC-style
>
I am also not able to figure out another use case than the IN predicate so
I am for always considering IN predicates as multi-valued.
On 9 September 2016 at 14:20, Steve Ebersole wrote:
> To be clear, this is the feature that lets you define a query like:
>
> select ...
yes I also believe it was a mistake
On 2 September 2016 at 12:34, Sanne Grinovero wrote:
> Sebastian Laskawiec pointed out that there is indeed a submodule,
> introduced by this commit:
>
> https://github.com/hibernate/hibernate-orm/commit/
>
I'm fine with combining native and JPA events handling, about the second
point, ideally I would change the signature but due to the problems you
listed I vote for the in-line solution.
On 30 August 2016 at 19:20, Steve Ebersole wrote:
> Any thoughts on the JpaIntegrator
I would prefer to postpone JavaMoney/Moneta integration to 6.0.
In case this is not possible I agree with including also the CDI work.
On 17 Aug 2016 21:56, "Steve Ebersole" wrote:
> For whatever reason discussion about JavaMoney/Moneta support has heated up
> again the
For details:
http://in.relation.to/2016/08/04/hibernate-orm-522-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On 25 Jul 2016 19:29, "Steve Ebersole" wrote:
>
> I wanted to start a consolidated discussion about multi-load support.
This
> relates to a few Jiras, questioning a few different aspects of its current
> behavior:
>
> https://hibernate.atlassian.net/browse/HHH-10984
>
On 7 July 2016 at 15:43, Steve Ebersole <st...@hibernate.org> wrote:
> On Thu, Jul 7, 2016 at 3:58 AM andrea boriero <and...@hibernate.org>
> wrote:
>
>> On 6 July 2016 at 21:01, Steve Ebersole <st...@hibernate.org> wrote:
>>
>>>
>>> One o
On 6 July 2016 at 21:01, Steve Ebersole wrote:
> This is something that has been bothering me for a long time. HHH-6328[1]
> is a specific example. Basically we are very inconsistent in how we
> attempt to match up table and column names, especially when there are
> naming
>
> On 1 July 2016 at 09:13, andrea boriero <and...@hibernate.org> wrote:
> > For details:
> > http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
> > ___
> > hibernate-dev mailing list
> > hibernat
sorry for the previous wrong subject,
Hibernate ORM 5.2.1.Final has been released
For details:
http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
For details:
http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
the annotation was introduced with
https://hibernate.atlassian.net/browse/HHH-6841
the reason seems to provide the ability add different reasons for each
Dialect.
On 8 June 2016 at 14:19, Vlad Mihalcea wrote:
> Hi,
>
> While writing a cross-dialect test, I bumped into
it sounds reasonable to me
On 7 June 2016 at 10:57, Vlad Mihalcea wrote:
> To get a picture of why we need this, consider the following example from
> the docs:
>
> Stream
I think at the moment if an issue affects 5.1 we should apply the fix.
But I may be wrong.
On 31 May 2016 at 12:53, Vlad Mihalcea wrote:
> Hi,
>
> I have backported some fixed to 5.1, and I'm not sure if that was the right
> thing to do.
> I know that for 5.0 we should
what about adding a
catch(ObjectNotFoundException onfe){
pe = new OptimisticLockException( e.getMessage, e);
}
to the existing try/catch that encloses the entity =
sharedSessionContract.load( sose.getEntityName(), identifier ) ?
On 17 May 2016 at 13:32, Vlad Mihalcea
Having a Strategy gives us more flexibility so +1.
About the expectations I think what Vlad says is reasonable.
On 25 April 2016 at 06:04, Vlad Mihalcea wrote:
> Your second email summarizes my thoughts as well. If we can separate the
> exception handling in two
Welcome Mincong!!!
On 22 April 2016 at 22:20, Mincong Huang wrote:
> Hi everybody,
>
> Thanks for accepting my application of GSoC !! Really excited to having
> chance to work the hibernate team. I'm so happy to see this email. It's
> just
> like a dream, can't believe it
+1 SharedSessionContractImplementor <- (Session
Implementor & StatelessSessionImplementor)
On 15 April 2016 at 14:30, Steve Ebersole wrote:
> So here is what I ended up doing, with one questionable decision which I'll
> highlight below.
>
> First, the existing situation...
I'm working on https://hibernate.atlassian.net/browse/HHH-10605;
for the https://hibernate.atlassian.net/browse/HHH-10515 I have two
different PR:
https://github.com/hibernate/hibernate-orm/pull/1264
https://github.com/hibernate/hibernate-orm/pull/1263
Andrea
On 11 April 2016 at 18:12, Vlad
+1
in my opinion at some point we will have to move to java8 and Hibernate 6.0
for me is a good candidate.
On 30 March 2016 at 12:40, Vlad Mihalcea wrote:
> +1
>
> Same opinion. Hibernate 6.0 should use Java 8 too. Most projects already
> use Java 1.8, and most
- not more than an hour but I noticed checkstyle on my machine has a
huge impact on the overall build time
On 1 March 2016 at 13:56, Sanne Grinovero <sa...@hibernate.org> wrote:
> On 1 March 2016 at 13:49, andrea boriero <drebor...@gmail.com> wrote:
> > checkStyl
checkStyle takes a lot of time
On 1 March 2016 at 13:17, Vlad Mihalcea wrote:
> 90 minutes is indeed too much, especially since the tests only take 25
> minutes:
>
> http://ci.hibernate.org/job/hibernate-orm-master-h2/1392/testReport/
>
> Could that check style plugin
Hi Martin,
welcome to the "committers club" and thanks a lot for you help.
Andrea
On 25 February 2016 at 18:46, Sanne Grinovero wrote:
> Hi all,
> Martin has been contributing to Hibernate Search since a year, and
> developed some very interesting extensions this summer
+1 for `--action` option with "create", "drop", "create-and-drop", and
"none"
not sure if as default value is better "create" or "create-and-drop"
On 3 February 2016 at 17:21, Steve Ebersole wrote:
> For anyone familiar using SchemaExport from the command line... Am I
>
i think it's better to drop
On 2 February 2016 at 21:10, Steve Ebersole wrote:
> Part of the work here is going to require significant changes
> to org.hibernate.tool.hbm2ddl.SchemaExport,
> org.hibernate.tool.hbm2ddl.SchemaUpdate
> and
I agree with providing a specific property to enable this behaviour.
I noticed also that handleAndClearWarnings(Connection
connection,WarningHandler handler) does the walking without checking for
the log level.
On 28 January 2016 at 07:59, Gunnar Morling wrote:
> Is
the failure is caused by the javadoc of
AvailabeSettings#GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITIONS
I'm fixing it
On 26 January 2016 at 15:55, Vlad Mihalcea wrote:
> I could replicate it on my local machine too:
>
> javadoc: error -
ition()} and {@link
javax.persistence.JoinColumn#columnDefinition}
really frustrated :(
On 26 January 2016 at 16:14, Steve Ebersole <st...@hibernate.org> wrote:
> Yes, I just found that too. But what specifically? I found it by brute
> force lol
>
>
> On Tue, Jan 26
I like it
On 25 January 2016 at 18:50, Steve Ebersole <st...@hibernate.org> wrote:
> Right
>
> On Mon, Jan 25, 2016 at 12:41 PM andrea boriero <drebor...@gmail.com>
> wrote:
>
>> do you mean to extend javax.persistence.Parameter with a sort
>> of enablePas
do you mean to extend javax.persistence.Parameter with a sort
of enablePassingNulls() method?
On 25 January 2016 at 17:56, Steve Ebersole wrote:
> HHH-9548[1] handles the question of what to do with null/unset parameter
> values in regards to calls to stored-procedures via
the problem seems related with the file name
/2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v..erb
instead of
/2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v.*html*
.erb
On 13 January 2016 at 20:22, Steve Ebersole wrote:
> Ok, that
I'm not against the use of Java 8 letting AnimalSniffer guarding for
compatibility,
but I understand this can cause some problems so I'm ok with removing Java
8 usage from tests.
On 12 January 2016 at 10:07, Gunnar Morling wrote:
> @Vlad, what Java 8 syntax specifically
Hi Vlad,
you mean we should provide that dependency, don't you?
On 6 January 2016 at 16:30, Vlad Mihalcea wrote:
> Hi,
>
> Since the Hibernate core relies on the JTA dependency, I think we shouldn't
> provide that dependency.
> When someone doesn't want it he should
Also for me +1
On 26 Dec 2015 19:29, "Sanne Grinovero" wrote:
> On 26 December 2015 at 16:55, Steve Ebersole wrote:
> > +1 from me on the concept.
> >
> > Of course the problem is always the resources needed keep that going.
> But
> > if you are
i think you are using java 7 instead of java 8..
On 15 December 2015 at 20:32, Scott Marlow wrote:
> Hi,
>
> I created a new Java project for the folder containing Hibernate master
> and imported the gradle build file (accepted defaults). When I tried
> running a unit test,
cleaned up :)
On 5 December 2015 at 15:27, Vlad Mihalcea wrote:
> Hi,
>
> Can someone make me admin as well, as I can help with the cleaning as well.
> Maybe we can integrate the Akismet spam filter on the forum. What do you
> think?
>
>
after reading your mail, I'm more inclined towards the solution you started
implementing in SQM-28-2.
https://github.com/sebersole/hibernate-semantic-query/blob/SQM-28-2/hibernate-sqm/src/main/java/org/hibernate/sqm/domain/DomainMetamodel.java
Just a clarification, what do you mean when you say
+1
On 24 November 2015 at 15:58, Sanne Grinovero wrote:
> Hi all,
> GitHub now provides an option to:
> - prevent pushing with the "force" option to a specific branch
> - prevent people to delete a specific branch
>
> Considering our workflow and also to prevent user
; I changed it now, let me know if it doesn't work.
>
> Sanne
>
> On 15 November 2015 at 20:32, andrea boriero <drebor...@gmail.com> wrote:
> > it's seems orm-5.0-h2 suffers the same problem.
> >
> > On 15 November 2015 at 00:48, andrea boriero <drebor...@gmail