Hi,
I have generated the javadoc locally and it looks fine. It seem int the
http://docs.jboss.org/hibernate/orm/4.3/javadocs/org/hibernate/Session.html
source all the and are escaped with lt; gt; . Could someone tell me
how this javadoc was generated?
Andrea
On 18 June 2014 14:58, Emmanuel
I have applied the patch for the jira
https://hibernate.atlassian.net/browse/HHH-9369 to the following branches:
- master
- 4.3
do I have to apply it also to 4.2?
Thanks,
Andrea
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
for me at the moment it would be 6pm and it should be good.
On 21 March 2015 at 21:08, Steve Ebersole st...@hibernate.org wrote:
Gail and I discussed Jira a little bit last week and how to best manage
scheduling issues.
We both agreed that a team get together, either weekly or
Hi Gunnar,
at the moment I cannot figure out any problem or anything you are missing,
the solution seems good :)
On 30 April 2015 at 09:08, Gunnar Morling gun...@hibernate.org wrote:
Steve, Andrea,
For OGM we need to store certain data in the scope of a transaction;
specifically this
I agree with the Beta2 in order to give time to try out the Transaction
Changes :)
+1
On 29 April 2015 at 16:20, Steve Ebersole st...@hibernate.org wrote:
I had originally planned on today's release being the first CR for 5.0. I
am re-thinking that now. Here is why...
1) If we were to
(the *Inflow contract, Andrea I
thought we had decided to rename that interface as well?)?
On Thu, Apr 30, 2015 at 4:02 AM, andrea boriero drebor...@gmail.com
wrote:
Hi Gunnar,
at the moment I cannot figure out any problem or anything you are
missing,
the solution seems good :)
On 30
I have spotted the problem and I'm fixing the infinispan tests.
On 9 May 2015 at 19:23, Steve Ebersole st...@hibernate.org wrote:
I pretty routinely run into problems running the testsuite in infinispan.
Generally the failures are transient. Just try running it again. If it
fails the same
I'm using your version
On 19 May 2015 at 04:01, Steve Ebersole st...@hibernate.org wrote:
The recent discussion on Checkstyle got me thinking about best ways to
share/distribute code styles for IDE setup. Storing them in the project
itself is not very workable for IntelliJ at least. I
I would mantain all 5.x in the same changelog file and may be the previous
one.
On 29 May 2015 at 12:32, Sanne Grinovero sa...@hibernate.org wrote:
I wouldn't stay awake at night because of that :) maybe only if the
file gets huge?
It's useful for people migrating, but since I doubt someone
I noticed the problem only when i run the build with AVA6_HOME set
On 19 August 2015 at 13:27, Sanne Grinovero sa...@hibernate.org wrote:
Hi Gail,
I tried to build it as well but I couldn't reproduce the problem; how
are you building it to trigger the error? Could you confirm which
commit
yes Steve I'm more familiar with Antlr4 ( but not 3) and I gave a look at
your poc.
Apart some problems to fully understand the semantic model (due to my lack
of a complete knowledge of the domain problem),
I agree with you about the simplicity and elegance of the grammar for
HQL recognition
and
using generated tree walkers.
On Wed, Aug 19, 2015 at 12:27 PM Steve Ebersole st...@hibernate.org
wrote:
I agree. Its my biggest hang up with regard to using Antlr 4. Actually,
its my only hang up with Antlr 4, but its a huge one.
On Tue, Aug 18, 2015 at 9:30 AM andrea boriero drebor
(Semantic Query Model) here. The top package being
org.hibernate.sqm.
These changes already illustrated some tighter couplings then I had
intended, so it was a good exercise. I'll push once I get those couplings
cleaned up.
On Fri, Aug 21, 2015 at 2:35 PM andrea boriero drebor...@gmail.com
Ebersole st...@hibernate.org
wrote:
Ok, then lets plan on next Tuesday on HiptChat...
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Hibernate+ORM+Triage+Meetingiso=20150721T13p1=24
On Tue, Jul 14, 2015 at 12:32 PM andrea boriero drebor...@gmail.com
wrote:
I have
-dev] ORM Team triage meeting
Big +1 from me -- I'd be more than happy to be involved.
- Original Message -
From: andrea boriero drebor...@gmail.com
To: Steve Ebersole st...@hibernate.org
Cc: hibernate-dev hibernate-dev@lists.jboss.org
Sent: Sunday
no objections
On 11 November 2015 at 17:55, Steve Ebersole wrote:
> I'd like to more formally deprecate the legacy bytecode enhancement
> starting in 5.0.4 and remove it in 5.1.
>
> The new code is superior and already feature compatible back to 5.0 Final.
>
> Any
Am I wrong or Jenkins is not building anymore hibernate-orm?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
it's seems orm-5.0-h2 suffers the same problem.
On 15 November 2015 at 00:48, andrea boriero <drebor...@gmail.com> wrote:
> Thanks Sanne
> On 14 Nov 2015 20:28, "Sanne Grinovero" <sa...@hibernate.org> wrote:
>
>> Looks like you were right.
>>
; 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
I vote for November 18
On 3 Nov 2015 18:36, "Steve Ebersole" wrote:
> Keeping up with the 4 week timebox for 5.0 bugfix releases unfortunately
> puts them on bad days with the upcoming holidays.
>
> 5.0.4 would hit Nov 25th which is the day before Thanksgiving here in the
>
sorry but I cannot attend the today triage meeting
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I don't figure out the use cases for @Formula on @Id as well
On 7 October 2015 at 10:21, Davide D'Alto wrote:
> What's the use case? A user that doesn't want to store the @Id but want it
> to be available when loading the entity?
>
> Davide
>
> On Wed, Oct 7, 2015 at 2:37
od idea to give a better
> indication tat this is not supported aside from some deeply nested NPE .
>
> On Wed, Oct 7, 2015 at 5:51 AM andrea boriero <drebor...@gmail.com> wrote:
>
>> I don't figure out the use cases for @Formula on @Id as well
>>
>> On 7 October 2015 a
In my opinion if we want to allow aliases overriding the scope should
follows the Java rules, it's easier to understand for a Java developer and
the second query should just be considered a bad written one.
On 7 October 2015 at 15:27, Steve Ebersole wrote:
> >
> > > Here
I have just modified the post, need only to push.
Emmanuel can you just take care of mails, g+ etc?
On 9 July 2015 at 17:16, Emmanuel Bernard emman...@hibernate.org wrote:
I’ll do this.
On 09 Jul 2015, at 15:35, Steve Ebersole st...@hibernate.org wrote:
Too late now. I am off for some
gt; full git clone each time.
>
> Thanks,
> Sanne
>
> On 14 November 2015 at 14:40, andrea boriero <drebor...@gmail.com> wrote:
> > Am I wrong or Jenkins is not building anymore hibernate-orm?
> > ___
> > hibernat
+1
On 27 August 2015 at 23:24, Steve Ebersole st...@hibernate.org wrote:
+1
On Thu, Aug 27, 2015 at 5:12 PM Gail Badner gbad...@redhat.com wrote:
Just a gentle reminder that, in keeping with our project's guidelines[1],
the 4.2 and 4.3 branches will no longer be actively maintained now
+1 for ~
On 28 August 2015 at 15:02, Steve Ebersole st...@hibernate.org wrote:
What do y'all think of using a symbol like ~ for this? The idea would be
similar to the wavy equals from logic used to denote approximately
equals.
On Thu, Aug 27, 2015 at 7:05 AM andrea boriero
at 8:45 AM andrea boriero drebor...@gmail.com
wrote:
I see,
Thanks
On 25 August 2015 at 13:17, Steve Ebersole st...@hibernate.org wrote:
from A a where a.b in (from B b ..) and a.c in (from C c ...) ...
But regardless, the children are not important for a stack, just the
parent. As I said
i like the idea of matches operator for dealing with is null.
+1
On 26 August 2015 at 19:32, Steve Ebersole st...@hibernate.org wrote:
https://hibernate.atlassian.net/browse/SQM-11
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
Thanks Gunnar
On 4 September 2015 at 08:57, Gunnar Morling wrote:
> Hi,
>
> As reported in the forum [1], the ORM 5.0.1 ZIP provided on
> SourceForge was corrupted for some reason, it could not be opened.
>
> I've replaced it with the version from BinTray which is valid
Hi Stevej
I'm playing with you idea to remove the parent/child from the FromClause
and introduce such a structure in the FromClauseProcessor.
just a question, in the current implementation a fromClause can have more
than one child fromClause , but I cannot figure out when this happen :(
Thanks
maintained because I used them for tests.
On Tue, Aug 25, 2015 at 6:53 AM andrea boriero drebor...@gmail.com
wrote:
Hi Stevej
I'm playing with you idea to remove the parent/child from the FromClause
and introduce such a structure in the FromClauseProcessor.
just a question, in the current
since Hibernate makes this assumption I think it's fine to enforce that.
On 15 September 2015 at 17:36, Steve Ebersole wrote:
> We have a Pull Request[1] to add a feature to allows Dialects to enforce
> that all columns making up a primary key are defined as non-nullable.
>
I'm working on https://hibernate.atlassian.net/browse/HHH-9996
and I stumbled across the following test:
org.hibernate.envers.test.integration.basic.ClassicQueryTranslatorFactoryTest
I run the test not only with Derby but also with PostgreSQL and the test
fails for both.
The query:
select e__
which test (method) fails. But I do not see a place where the user
> is executing any HQL. So that tells me this is potentially a problem
> specifically in how envers builds a query internally somewhere. And that,
> if true, is something we should address.
>
> So which t
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
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,
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
+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'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
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
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 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
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
+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
>
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
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 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'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
- 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
+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
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
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
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
+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...
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
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 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
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
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
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:
>
+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
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).
>
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
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
+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
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
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
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
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
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 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 ...
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
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
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.
+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
>
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 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.
>
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
+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