On Mon, Mar 28, 2016 at 1:22 PM Lovro Pandzic
wrote:
> I am confused how you are "mind mapping" PreparedStatement parameters and
>> entity construction into the same conversation. We are not instantiating
>> entities based on PreparedStatement parameters
>>
>
> I'm
We have been having a few side discussions about plans for 6.0, and I
thought it would be a good idea to consolidate them together.
1. Incorporate the SQM work. Lots of pieces go into this:
1. Replacing the interpretation of HQL/JPQL and Criteria queries.
2. *Possibly* leveraging
Great, thanks!
On Wed, Mar 30, 2016 at 1:39 PM Vlad Mihalcea <mihalcea.v...@gmail.com>
wrote:
> Sure, I'll add a new one containing the email conclusions and a link to
> HHH-10014 and commit it tomorrow.
>
> Vlad
>
> On Wed, Mar 30, 2016 at 9:23 PM, Steve Ebersole <s
der the
> https://hibernate.atlassian.net/browse/HHH-10014 issue?
> I can do it tomorrow.
>
> Vlad
>
> On Wed, Mar 30, 2016 at 5:40 PM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> The code is wrong in
>> the GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITION
The code is wrong in
the GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITIONS case; the java doc
is correct. By default we should not be skipping columnDefinitions while
applying global-quoting to be sec compliant.
In the second case, its the opposite... the javadoc is wrong.
Keyword-quoting
One question we have discussed but never really answered with regard to ORM
as we work on SQM has to do with the version of Java we would baseline on.
Currently ORM 5.0 and 5.1 continue the tradition of still running in Java 6
runtimes. Java 8 has since come along and offered some JDK "goodies"
t be public or
> protected."
>
> The property names that might be used as constructor arguments should
> probably be annotated with a @ConstructorArg annotation and possibly
> specify the argument order in the construction newInstance(args) invocation.
>
> So, there are a lot
Commented on the Jira.
I am confused how you are "mind mapping" PreparedStatement parameters and
entity construction into the same conversation. We are not instantiating
entities based on PreparedStatement parameters
On Fri, Mar 18, 2016 at 2:32 AM Lovro Pandzic
How does one reference a CTE across multiple deletes via JDBC? A CTE, by
definition, is available only during the execution of a single query. In
most databases you "work around" that by grouping statements into a block
(GO, BEGIN/END etc). This is what JDBC poorly attempt to mimic with
It looks like it changed during 3.6 -> 4.0, reverting back to ON_CLOSE. I
agree it should changed to AFTER_TRANSACTION, however I would only change
it on master.
For the other branches, if anything, just update the doc.
On Thu, Mar 3, 2016 at 12:40 AM Vlad Mihalcea
To be honest, I think its best if we somehow notify you for issues fixed
that we think should be considered for inclusion on 5.0 branch and you can
decide. A label or a filter. Something like that
On Wed, Mar 16, 2016 at 5:30 PM Gail Badner wrote:
> Please do not backport
Personally I think using IncomparableComparator or null here makes the most
sense. I'm not really sure what the sort ordering of a byte array would
"mean".
On Thu, Mar 10, 2016, 1:41 AM Gail Badner wrote:
> I've created a pull request implements option A) (creates
d that
> not having a specific extension was not hurting performance and
> feasibility.
>
> On Wed 2016-03-09 22:49, Steve Ebersole wrote:
> > A PAR is just an archive with a META-INF/persistence.xml file in it. The
> > JPA spec does cover this. The extension is irrelevant.
&
A PAR is just an archive with a META-INF/persistence.xml file in it. The
JPA spec does cover this. The extension is irrelevant.
On Wed, Mar 9, 2016 at 4:08 PM Sanne Grinovero wrote:
> I remember JBoss had "HAR" deployments to package Hibernate models and
> PU
Are you just asking if it is ok to fix this is 4.3? I am not following
exactly, just trying to make sure I understand your question.
On Mon, Mar 7, 2016 at 12:43 PM Vlad Mihalcea
wrote:
> Hi,
>
> I was involved in trying to replicate the following issue:
>
>
Anyone plan on looking at these frequent transient failures anytime soon?
If not, I plan on disabling this from running automatically. It's just
white noise at this point.
-- Forwarded message -
From: Hibernate CI
Date: Wed, Mar 2, 2016 at 8:22 AM
Subject:
Another thing Andrea and I did today was to identify that our current
approach to handling keywords (to allow for "keywords as identifier")
caused quite major performance problems.
So we have started to rewrite how keywords and "keywords as identifier"
work. We have consistently seen an
Yes, it has a *huge* time hit. If you look at the Gradle perf breakdown
IIRC the task with the most time is actually check
On Tue, Mar 1, 2016 at 8:03 AM andrea boriero wrote:
>- not more than an hour but I noticed checkstyle on my machine has a
>huge impact on
Correct. hibernate-infinispan can use Java 8. As Sanne says, Infinispan
itself requires Java 8 so limiting hibernate-infinispan to > 8 really makes
no sense,
On Tue, Mar 1, 2016 at 3:03 PM Sanne Grinovero wrote:
> In general, probably yes. The Infinispan module is a bit
Today Andrea and I spent the day investigating interpreting of HQL/JPQL
into SQM in just a single phase as opposed to the previous 2-phase approach
(all FromClauses as first phase, and then the rest of statements as
second). Andrea had the idea to try this again (both he and I tried
previously),
wiki/Java_Persistence/Relationships#Lazy_Fetching
>
> Vlad
>
> On Sun, Feb 28, 2016 at 7:08 PM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> The Hibernate team argued against this, but we were outvoted. So...
>> sorry I cannot "justify it"
The Hibernate team argued against this, but we were outvoted. So... sorry
I cannot "justify it" ;)
Obviously as our previous default shows we believe the associations should
be lazy by default.
On Sun, Feb 28, 2016 at 11:00 AM Vlad Mihalcea
wrote:
> Hi,
>
>
> Do you
like there
>> is no free, robust, open-source, embeddable, JSR-107-compatible cache
>> implementation.
>>
>> 2016-01-14 16:31 GMT+02:00 Steve Ebersole <st...@hibernate.org>:
>>
>>> So then it sounds like "no" to this, which is fine. W
m computador sem vírus e protegido pelo
> Avast.
> www.avast.com <https://www.avast.com/sig-email>
> <#msg-f:1526971223964960053_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Feb 23, 2016 at 9:36 AM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> W
, Feb 23, 2016 at 3:31 AM Emmanuel Bernard <emman...@hibernate.org>
wrote:
> To be honest I cannot make up my mind to decide which behavior is more
> correct. I can see both as valid.
>
> > On 22 Feb 2016, at 18:07, Steve Ebersole <st...@hibernate.org> wrote:
&
Karel, a user was asking about problems using the hibernate-spatial mailing
list on IRC which precipitated a discussion about how we want deal with
these things moving forward. For example, the
http://www.hibernatespatial.org/ site is still up and running and really
has no indication that the
For Twitter, I don't know. As for Google+ you have to tell me your Google+
name as I mentioned when I set that service up. I tried searching for you,
but found nothing.
On Wed, Feb 17, 2016 at 6:57 PM Gail Badner wrote:
> I was able to announce on
alize the doc under hibernate.org.
>
> On 16 févr. 2016, at 22:15, Steve Ebersole <st...@hibernate.org> wrote:
>
> No, personally I am talking strictly about the
> hibernate.org/orm/documentation nav
>
>
> On Tue, Feb 16, 2016 at 3:14 PM Vlad Mihalcea <mihalcea.v...@gmail.c
I just moved the other to 5.0.9 as well.
On Tue, Feb 16, 2016 at 4:25 PM andrea boriero wrote:
> Hi Gail,
>
> for https://hibernate.atlassian.net/browse/HHH-10250 I have just removed
> it from the 5.0.8 release, we are waiting for a test case.
>
>
> On 16 February 2016
Vlad working on it as he is our doc focused expert.
>> Davide and I can offer Awestruct assistance of course.
>>
>> > On 12 févr. 2016, at 19:12, Steve Ebersole <st...@hibernate.org> wrote:
>> >
>> > Emmanuel, Davide, etal...
>> >
>> >
We have been having an ongoing discussion about using Java 8 features in
tests. My only argument against that was the fact that doing so makes it
impossible to run tests in IDE (IntelliJ at least) unless I set the
"language level" for the whole module to Java 8 which means I possibly miss
using
e call to `#registerCallReturn` tells us completely everything we need to
make a `{?=call(...)}` call instead of the `{call(...)}` form.
For JPA the only options really are a hint or an extension. With the hint
approach, we pretty much have to follow the 3-point assumptions I set above
in terms o
; that return a value.
> Have you ever seen such a function call working with named parameters?
>
> Vlad
>
> On Mon, Feb 15, 2016 at 7:43 PM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> On Mon, Feb 15, 2016 at 10:16 AM Vlad Mihalcea <mihalcea.v...@gmail
tangent... I wonder if we maybe want to wander
>>> into trying to
>>> leverage
>>> java.sql.DatabaseMetaData#getFunctions/java.sql.DatabaseMetaData#getProcedures
>>> to just automatically handle the difference (as opposed to the need for the
>>> user to expl
On Mon, Feb 15, 2016 at 10:16 AM Vlad Mihalcea
wrote:
> The problem with naming the method as
> "ProcedureCall#setTreatAsFunction(boolean isFunction)" is that the term
> "function" is very leaky.
>
The distinction being made is whether we need to use the JDBC function
he following hint:
>
> org.hibernate.registerFunctionReturnType
>
> The logic should be just like for the
> ProcedureCall#registerFunctionReturnType(Class type).
>
> Does it sound reasonable?
>
> Vlad
>
> On Mon, Feb 15, 2016 at 4:34 PM, Steve Ebersole <st...@hibe
parameter.
On Mon, Feb 15, 2016 at 8:27 AM Steve Ebersole <st...@hibernate.org> wrote:
> Well as my todo comment says:
>
> // todo : how to identify calls which should be in the form `{? = call
> procName...}` ??? (note leading param marker)
>
> //more than likely this
Well as my todo comment says:
// todo : how to identify calls which should be in the form `{? = call
procName...}` ??? (note leading param marker)
//more than likely this will need to be a method on the native
API. I can see this as a trigger to
//both: (1) add the `? = ` part and
s :)
>>
>> 2015-03-22 2:38 GMT+02:00 Steve Ebersole <st...@hibernate.org>:
>>
>>> So it sounds like JSR 354 may not be included in Java 9. Do we still
>>> want
>>> to support this for ORM 5? I am not sure if "moneta" requires J
> I remember I saw the old-style guide right after the 5.1 release.
>
> Vlad
>
> On Fri, Feb 12, 2016 at 6:44 PM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> That's strange. As far as I know we actually cannot delete from there.
>> At
>> least I wa
That's strange. As far as I know we actually cannot delete from there. At
least I was not allowed to delete from orm/5.1 yesterday when I was doing
work.
As for restoring, I do not know if backups are kept. We could open a
ticket and see. If not, do y'all build docs into the release bundles?
What's the level of versions for the validator docs on the server? x.y?
On Fri, Feb 12, 2016 at 10:59 AM Steve Ebersole <st...@hibernate.org> wrote:
> If the old style guides were there after the release, but gone since I
> uploaded yesterday then maybe my upload also affected t
those.
Sorry (if that really was me).
On Fri, Feb 12, 2016 at 10:53 AM Steve Ebersole <st...@hibernate.org> wrote:
> But thats a completely different URL Vlad. That is a UR to the
> hibernate.org server. Not the doc server.
>
> On Fri, Feb 12, 2016 at 10:48 AM Vlad Mi
Sanne. Emmanuel.. the rsync is already done. Docs from 3.0->5.3 (as of the
last release on SF for that x.y).
On Fri, Feb 12, 2016 at 12:12 PM Steve Ebersole <st...@hibernate.org> wrote:
> Emmanuel, Davide, etal...
>
> I think I want to redo that decision to put versione
ll the way back till 3.0. So if you are at 4.2, you are
> almost there :)
>
> 2016-02-12 18:31 GMT+01:00 Steve Ebersole <st...@hibernate.org>:
> > so far I have downloaded back to 4.2. Should I stop at 5.0?
> >
> >
> > On Fri, Feb 12, 2016 at 11:25 AM Gunnar M
Vlad, here is the ongoing work for this on the staging branch for the
website...
https://github.com/hibernate/hibernate.org/tree/staging/orm/documentation/5.1
On Fri, Feb 12, 2016 at 12:05 PM Steve Ebersole <st...@hibernate.org> wrote:
> Vlad, today I will work updating the websit
Vlad, today I will work updating the website for ORM. Versioned
information (documentation) is very difficult to deal with there (imho)
On Fri, Feb 12, 2016 at 12:01 PM Steve Ebersole <st...@hibernate.org> wrote:
> I went all the way back to 3.0. rsync started
>
> On Fri, Feb 12
ri, Feb 12, 2016 at 12:05 PM Steve Ebersole <st...@hibernate.org> wrote:
> Vlad, today I will work updating the website for ORM. Versioned
> information (documentation) is very difficult to deal with there (imho)
>
> On Fri, Feb 12, 2016 at 12:01 PM Steve Ebersole <st...@hibe
At this point the 5.1 documentation is all hosted[1] and the hibernate.org
website updated to reflect this[2].
Consolidating a lot of simultaneous discussions going on, the remaining
tasks imo:
1. Develop an answer for the SEO problem. Whether that can be achieved
continuing to use the
nguages.
> If the users haven't complained that we didn't maintain the non-English
> docs,
> I'd suppose we could simply focus on the English version only.
>
> Google Chome does a decent job when translating articles from English to
> other languages anyway.
>
> Vlad
>
&
We can make that change in SQM, but its not an option to change that
before.
But Gunnar your load use case would be a bug if true
On Thu, Feb 11, 2016, 7:55 AM Vlad Mihalcea wrote:
> Hi,
>
> True. I also wondered why don't we use the DISTINCT as the default
>
On Thu, Feb 11, 2016 at 2:38 PM Hardy Ferentschik
wrote:
> Hi,
>
> > Ok, then I will drop the 'en-US' part from the path.
>
> +1
>
> > But to be consistent, I think we should rename the "html" in these
> asciidoc
> > paths to "html_single".
>
> but why even make this
The translations of the ORM documentation (at least) is completely out of
date. Has been for many years. To the point where we stopped even
publishing translations.
So at this point, as we migrate to Asciidoc(tor) and make changes to doc
hosting do we plan for eventual translations? Or do we
Dialect#defaultProperties is a broken concept IMO. It was an attempt to
avoid an explosion of methods such as the one you propose. I personally
agree that the specific methods are better.
However, all that said.. I do not believe what you say is accurate. At
least not looking at the code. In
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I need to deal with the new link ontology we decided on for the doc server
anyway
On Wed, Feb 10, 2016 at 1:08 PM Steve Ebersole <st...@hibernate.org> wrote:
> no, I'll do it
>
> On Wed, Feb 10, 2016 at 1:05 PM Vlad Mihalcea <mihalcea.v...@gmail.com>
> wrote:
>
>
The release build is done. Push away!
On Wed, Feb 10, 2016 at 11:14 AM Steve Ebersole <st...@hibernate.org> wrote:
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
ORM 5.1 has just been released. See details @
http://in.relation.to/2016/02/10/hibernate-orm-510-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
2. 5.0
3. 4.3 (?)
4. 4.2 (?)
Gail, am I correct that you still run 4.2 and 4.3 as part of Red Hat
productization? To be honest, I am not even sure those builds (and maybe
even 5.0 at this point) should be updating the doc server.
On Wed, Feb 10, 2016 at 1:09 PM Steve Ebersole <
A related concern is a discussion I started before in regards to version
specific information on hibernate.org
Did we ever come to any conclusion about how (if) we were going to handle
that?
On Wed, Feb 10, 2016 at 1:40 PM Steve Ebersole <st...@hibernate.org> wrote:
> I fixed the
Bueller... ? ;)
Silence to me == I can do whatever I want... So if you have a need for
this, please speak up
On Tue, Jan 19, 2016 at 12:53 PM Steve Ebersole <st...@hibernate.org> wrote:
> There are a few reasons I want to remove Query#getReturnTypes. At least
> in its current form
This is going to have to wait post-5.1 as I mentioned earlier if this was
not ready prior to last week.
I have just too much on my plate to look at this over 2 days.
On Mon, Feb 8, 2016 at 12:29 AM Gail Badner wrote:
> The POC [1] assumes that we only need a single
I am working mainly on HHH-16 which requests adding support for
entity-joins (aka "ad hoc" joins).
So long-story-short, there is a simple solution with some limitations and
then a more correct solution that unfortunately requires a lot of rework in
the HQL parser.
The crux of the problem is
this
via hints just feels completely icky to me.
On Tue, Jan 5, 2016 at 12:11 PM Steve Ebersole <st...@hibernate.org> wrote:
> HHH-9548[1] presents an interesting conundrum in terms of how to handle
> null parameter values in regards to stored procedures and specifically in
> terms
ld not have to change.
>
> 2016-02-02 22:10 GMT+01:00 Steve Ebersole <st...@hibernate.org>:
> > Part of the work here is going to require significant changes to
> > org.hibernate.tool.hbm2ddl.SchemaExport,
> > org.hibernate.tool.hbm2ddl.SchemaUpdate and
> >
Just as a suggestion, we do not need to go to a "full on" clone for your
(1). A fat-jar, shaded-jar, should also do the
trick.
On Wed, Feb 3, 2016 at 7:54 AM Scott Marlow wrote:
> As modular classloading environments become more popular (e.g. WildFly,
> OSGi, Openjdk
-in the
replacement from upstream.
On Wed, Feb 3, 2016 at 7:58 AM Steve Ebersole <st...@hibernate.org> wrote:
> Just as a suggestion, we do not need to go to a "full on" clone for your
> (1). A fat-jar, shaded-jar, should also do the
> trick.
>
>
> On Wed, Feb 3, 2016 at 7:54 A
...@gmail.com> wrote:
> +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
n.
Anyone else find that extremely counter-intuitive? Any objection to
instead exposing an `--action` option that can be one of "create", "drop",
"create-and-drop", and "none"? And where "create-and-drop" is the default?
On Wed, Feb 3, 2016 at 6:50 AM Stev
,
or to simply drop those classes?
On Fri, Jan 29, 2016 at 1:15 PM Steve Ebersole <st...@hibernate.org> wrote:
> I am debating with myself about
> reusing `javax.persistence.schema-generation.database.action` and
> `javax.persistence.schema-generation.scripts.action`
> in terms o
want to break the contract of SchemaCreator and the other
> delegates.
>
> --Gunnar
>
>
>
>
> 2016-01-28 19:27 GMT+01:00 Steve Ebersole <st...@hibernate.org>:
> > For this to work will require some significant changes. The main one
> being
> > to combine
On Fri, Jan 29, 2016 at 10:40 AM Gunnar Morling <gun...@hibernate.org>
wrote:
> 2016-01-29 17:18 GMT+01:00 Steve Ebersole <st...@hibernate.org>:
> > I also plan on adding an @Incubating annotation for just such things :)
>
> Yes, please. We have an annotation @Exper
gun...@hibernate.org> wrote:
> Do you see any use case for accessing it reflectively at runtime?
>
> FWIW, OGM's @Experimental has CLASS retention, which I think is
> "enough retention" for its purpose.
>
> 2016-01-29 18:50 GMT+01:00 Steve Ebersole <st...@hibernate.org&
requires more.
>
>
> On 29 January 2016 at 18:06, Steve Ebersole <st...@hibernate.org> wrote:
> > I personally do not in terms of usage from ORM, nor in usage by ORM
> users
> > either. I do wonder about tooling though. Like would it be useful for a
> > tool
Per HHH-10487[1], I want to add an @Incubating annotation to mark APIs that
are still incubating. Specifically, what do y'all think of
`java.lang.annotation.RetentionPolicy#CLASS` versus
`java.lang.annotation.RetentionPolicy#RUNTIME`?
[1] https://hibernate.atlassian.net/browse/HHH-10487
nt for the split since we have to account for JPA, and that
model fits both. I was just curious
On Fri, Jan 29, 2016 at 12:01 PM Steve Ebersole <st...@hibernate.org> wrote:
> On Fri, Jan 29, 2016 at 10:40 AM Gunnar Morling <gun...@hibernate.org>
> wrote:
>
>> 2016-
I do not know how to quantify "popularity", but I do know I have seen lots
of projects using travis for commit validation.
TBH my only concern would be access to the results. And that is more an
unknown. As I have never used Travis CI I do not know how its UI works.
Guillaume do you have
tes would do their thing. If it's that, I can try
> and help out with it.
>
> Regarding the release schedule, I'd personally be fine with pushing it
> a bit back, but then I don't know whether there are any other hard
> timelines to be met.
>
>
> 2016-01-19 16:25 GMT+01:00
+1 to allow a setting to control *logging* of SQLWarnings. I find it silly
that MySQL handle it this way (I can only find reference to MySQL when I
google search for `JDBC getSQLWarnings performance`) in terms of it being
such a performance hit.
However I really do not like the idea of fencing
Just pesky things like resources ;)
On Wed, Jan 27, 2016 at 12:43 AM Vlad Mihalcea
wrote:
> This must be done like insert but in reverse order. With inserts, we need
> to add parents first and children after, because of the foreign key
> constraints.
> For delete, we
istrations mentioned above. I will do this on master
(5.1). IMO we should also consider backporting this, but wanted to get
everyone's (anyone) thoughts first. Opinions?
On Tue, Jan 26, 2016 at 11:48 AM Steve Ebersole <st...@hibernate.org> wrote:
> This has come up again under H
Anyone know what is up with this Javadoc tool failure in these jobs? We've
had the same failure for the last few builds...
-- Forwarded message -
From: Hibernate CI
Date: Tue, Jan 26, 2016 at 4:09 AM
Subject: Build failed in Jenkins: hibernate-orm-master-h2
to
>> com.sun.tools.javadoc.AnnotationTypeElementDocImpl
>> :documentation:aggregateJavadocs FAILED
>>
>>
>> http://stackoverflow.com/questions/44853/why-am-i-getting-a-classcastexception-when-generating-javadocs
>>
>> I'll need to dig into it further
>>
>
This has come up again under HHH-10345[1].
The original request here claims that Oracle have deprecated LONG (
LONGVARCHAR) and LONG RAW (LONGVARBINARY). It refers to the 9i release
notes as "proof" of that[2]. The 9i release notes do mention LONG
(LONGVARCHAR)
datatype being deprecated.
Awesome! Congrats everyone, very exciting!
On Tue, Jan 26, 2016 at 10:11 AM Sanne Grinovero
wrote:
> Hello all,
> I'm thrilled to announce that there is now Eclipse tooling available
> to help developers using Hibernate Search.
>
> This was created by Dmitry Bocharov,
ht to stop the deployment)
until runtime.
The "win" for this approach however is that it would work in both 5.0 and
5.1.
So I think I will add that option, unless anyone has objections.
On Mon, Jan 25, 2016 at 12:02 PM Steve Ebersole <st...@hibernate.org> wrote:
> I have been in c
HHH-9993[1] is a request to extend IsolationDelegate to cater for
transaction hooks which do not need access to a JDBC Connection.
A quick primer for those unfamiliar, IsolationDelegate is a contract to
allow work to be done in a fashion that makes sure it is isolated from the
main Session
HHH-9548[1] handles the question of what to do with null/unset parameter
values in regards to calls to stored-procedures via
JPA's StoredProcedureQuery contract.
Do we just want to live with the overhead that comes from my last
comment[2]? Another option I see would be an extension
to
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 enablePassingNulls() method?
>
> On 25 January 2016 at 17:56, Steve Ebersole <st...@hibernate.org> wrote:
>
>>
gt;
> And none are using the listeners you listed. In the case of WildFly, I
> don't know of course about all the frameworks which are included in
> there.
>
> Sanne
>
> On 22 January 2016 at 23:58, Steve Ebersole <st...@hibernat
ategy-work/
>>>
>>> For sync: TRANSACTIONAL
>>>
>>>
>>> http://vladmihalcea.com/2015/06/01/how-does-hibernate-transactional-cacheconcurrencystrategy-work/
>>>
>>> Only the region strategy differs since it's not Ehcache, but everything
&g
e
>
> On 19 January 2016 at 22:30, Steve Ebersole <st...@hibernate.org> wrote:
> > Sanne, Gunnar any thoughts/input here?
> >
> >
> > On Tue, Nov 24, 2015 at 2:11 AM Konstantin Bulanov <bulan...@gmail.com>
> > wrote:
> >
> >> Hello, y
ntifiers.
>
> On 25 January 2016 at 18:21, Steve Ebersole <st...@hibernate.org> wrote:
> > Minor detail wrt method naming...
> >
> > Actually performing a org.hibernate.MultiIdentifierLoadAccess is
> currently
> > achieved via a method named `#multi
Gillaume, I am still seeing conflicts
On Wed, Jan 13, 2016 at 7:10 AM Guillaume Smet <guillaume.s...@gmail.com>
wrote:
> On Tue, Jan 12, 2016 at 6:40 PM, Steve Ebersole <st...@hibernate.org>
> wrote:
>
>> If you clean up the conflicts I can look for 5.1
>
e least making things consistent
> >> between SchemaExport and SchemaUpdate and also leaving APIs largely
> >> unchanged for the time being. With that I should be able to do it on
> >> the OGM side as you suggested, essentially ignoring the
> >> Target/Exporter stuff.
>
And please let's not take that to mean "let's add more tasks to 5.1 now..."
;)
On Fri, Jan 22, 2016 at 9:16 AM Steve Ebersole <st...@hibernate.org> wrote:
> I just pushed 5.1 back to Feb 10th in order to get all this work in.
>
> On Wed, Jan 20, 2016 at 6:
As part of the work on HHH-8076 for ORM 5.1 I am going to have to change
up, in some fashion, some or all of the following internal/spi contracts :
* org.hibernate.jpa.event.spi.jpa.Callback
* org.hibernate.jpa.event.spi.jpa.CallbackRegistry
* org.hibernate.jpa.event.spi.jpa.ListenerFactory
*
trouble for anyone, please speak up
asap. If not, I'll proceed.
Thanks!
On Fri, Jan 22, 2016 at 3:28 PM Steve Ebersole <st...@hibernate.org> wrote:
> As part of the work on HHH-8076 for ORM 5.1 I am going to have to change
> up, in some fashion, some or all of the following internal/s
, 2016 at 3:38 PM Steve Ebersole <st...@hibernate.org> wrote:
> If it matters, my plan is as follows...
>
> Currently JpaIntegrator is the central point for this processing. The
> general premise is that it builds a CallbackRegistry, a ListenerFactory
> and a CallbackPro
I would look at 2 things as I mentioned on HipChat yesterday...
1) Hibernate does have some capacity to do what you are expecting. There
are definitely some limitations to it. But the idea is called a
"backref". When building the metamodel for this, Hibernate should inject 2
synthetic backref
901 - 1000 of 3132 matches
Mail list logo