Won't there be many breaking changes moving to 6.0 anyhow? I can see
keeping the signatures the same in 5.x, but I, personally, am not as
concerned about keeping them the same moving to 6.0. I would certainly
try to make the migration as painless as possible.
I'm on the fence about whether empty-c
My one concern with doing this in 5.x is that we'd almost certainly change
the signature of EmptyCompositeStrategy as we transition to 6. 6.0 has a
real encapsulation of the embeddable in addition to the embedded. 5.x only
really keeps the embedded (CompositeType).
Anotger aspect that we have no
On Tue, Oct 17, 2017 at 12:55 AM Gail Badner wrote:
> >
> > WRT to the condition check, you suggest to "compare a primitive value in
> a
> > composite with the default for the primitive type (e.g, comparing an int
> > value with 0 instead of null)". That's not the best condition check. I
> was
On Sun, Oct 15, 2017 at 10:46 AM, Steve Ebersole wrote:
> On Fri, Oct 13, 2017, 3:35 PM Gail Badner wrote:
>>
>> Hi Steve,
>>
>> I'm circling back to this. Please see below...
>>
>> On Sat, Sep 2, 2017 at 8:47 AM, Steve Ebersole
>> wrote:
>> > I don't have the original email to reply to. So I'l
On Fri, Oct 13, 2017, 3:35 PM Gail Badner wrote:
> Hi Steve,
>
> I'm circling back to this. Please see below...
>
> On Sat, Sep 2, 2017 at 8:47 AM, Steve Ebersole
> wrote:
> > I don't have the original email to reply to. So I'll reply here.
> >
> > Overall, I had not really considered the primi
Hi Steve,
I'm circling back to this. Please see below...
On Sat, Sep 2, 2017 at 8:47 AM, Steve Ebersole wrote:
> I don't have the original email to reply to. So I'll reply here.
>
> Overall, I had not really considered the primitive attribute case, but yeah
> that's clearly an issue. My mistak
I don't have the original email to reply to. So I'll reply here.
Overall, I had not really considered the primitive attribute case, but yeah
that's clearly an issue. My mistake.
A) I agree that the con here is huge. Not the best option
B) Is close to better. We could certainly check this and
On 28 March 2017 at 10:03, Vlad Mihalcea wrote:
> There musts be a reason for choosing this ordering, but I can't figure out
> why the EntityDeleteAction was chosen to be executed last.
>
Isn't it simply to avoid foreign key constraints to explode? When you
update a reference to a foreign key *a
Thanks Vlad,
and for what it's worth, the tests for H2 run through.
Am 19.09.2016 um 17:10 schrieb Vlad Mihalcea:
> I can take a look on it tomorrow and let you know.
>
> Vlad
>
> On Mon, Sep 19, 2016 at 5:50 PM, Christian Beikov
> mailto:christian.bei...@gmail.com>> wrote:
>
> Hey everyone,
I can take a look on it tomorrow and let you know.
Vlad
On Mon, Sep 19, 2016 at 5:50 PM, Christian Beikov <
christian.bei...@gmail.com> wrote:
> Hey everyone,
>
> I'd like to get HHH-10229 fixed as I can't workaround it. I prepared the
> fix and a test(https://github.com/hibernate/hibernate-orm/
Thanks, Gunnar :)
On Mon, Jun 20, 2016 at 8:55 AM, Gunnar Morling
wrote:
> Hi Mincong,
>
> Seems you got an answer on SO already. Very glad to see you are making
> good progress!
>
> Cheers,
>
> --Gunnar
>
>
> 2016-06-18 17:05 GMT+02:00 Mincong Huang :
>
>> Hi everybody,
>>
>> I'm Mincong, your
Hi Mincong,
Seems you got an answer on SO already. Very glad to see you are making good
progress!
Cheers,
--Gunnar
2016-06-18 17:05 GMT+02:00 Mincong Huang :
> Hi everybody,
>
> I'm Mincong, your intern from Google Summer of Code. I'm working on
> a new implement of mass indexer for Hibernate
Well, it was more something like: the co-spec lead rules over the majority :)
Historically, very few implementations used proxies like Hibernate and
bytecode enhancement had (still has) its quirks.
A pretty bad and impactful decision unfortunately.
On Sun 2016-02-28 18:05, Steve Ebersole wrote:
>
But to me that is not a reason EAGER is the default. As the passage says,
LAZY is just a hint. So for a provider that does not support LAZY, EAGER
would be used instead anyway. No, some of the EG members specifically
argued for wanting to-one associations to be EAGER by default. IMO it was
a ba
Thanks,
Rhe only reason I found is this paragraph:
"The EAGER default for OneToOne and ManyToOne is for implementation reasons
(more difficult to implement), not because it is a good idea. Technically
in JPA LAZY is just a hint, and a JPA provider is not required to support
it, however in reality
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 remember why the JPA User
On 03/18/2015 02:56 PM, Scott Marlow wrote:
>
> On 03/18/2015 01:53 PM, Steve Ebersole wrote:
>> Out of curiosity though, since you want more and more and more things
>> pushed to "second phase bootstrapping", I am curious how this new
>> expectation plays in with that. Specifically, us "using"
On 03/18/2015 01:53 PM, Steve Ebersole wrote:
> Out of curiosity though, since you want more and more and more things
> pushed to "second phase bootstrapping", I am curious how this new
> expectation plays in with that. Specifically, us "using" Jandex will
> certainly include us accessing classes
Out of curiosity though, since you want more and more and more things
pushed to "second phase bootstrapping", I am curious how this new
expectation plays in with that. Specifically, us "using" Jandex will
certainly include us accessing classes, unless Jason has added the expanded
capabilities he a
Massive.
On Wed, Mar 18, 2015 at 12:44 PM, Scott Marlow wrote:
> On 03/18/2015 01:05 PM, Steve Ebersole wrote:
>
>> Well I should also clarify that currently we are not using Jandex. That
>> was all work done as part of the mapping/metamodel redesign which we
>> decided to push to 6.0.
>>
>
> I
On 03/18/2015 01:05 PM, Steve Ebersole wrote:
> Well I should also clarify that currently we are not using Jandex. That
> was all work done as part of the mapping/metamodel redesign which we
> decided to push to 6.0.
I assume you mean the master (5.0) code base doesn't use Jandex but it
looks li
Well I should also clarify that currently we are not using Jandex. That
was all work done as part of the mapping/metamodel redesign which we
decided to push to 6.0.
On Wed, Mar 18, 2015 at 10:22 AM, Steve Ebersole
wrote:
> I don't *think* we do, but it sounds like something we definitely need t
I don't *think* we do, but it sounds like something we definitely need to
make sure we aren't doing.
On Mar 17, 2015 8:41 AM, "Scott Marlow" wrote:
> Steve,
>
> Wildfly-dev [1] brings up a change expected for WildFly 10, to not
> reference the Jandex indexes after deployment completes. I'm curio
[mailto:gunnar.morl...@googlemail.com] On
Behalf Of Gunnar Morling
Sent: Thursday, February 12, 2015 12:43 AM
To: Haswell, Josiah D
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Question about substituting IDs in Hibernate OGM
2015-02-12 1:37 GMT+01:00 Haswell, Josiah D
tion to get it.
>
See above, you should take all the column values from the Person table (or
the Persistable table when working with SINGLE_TABLE). You can get the
table name from the given entity key. From the tuple context btw. you can
get the columns we actually need, so you don't need to fe
[mailto:gunnar.morl...@googlemail.com] On
Behalf Of Gunnar Morling
Sent: Wednesday, February 11, 2015 12:43 AM
To: Haswell, Josiah D
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Question about substituting IDs in Hibernate OGM
Hi Josiah,
It's great to hear that you are working
Hi Josiah,
It's great to hear that you are working an a backend for Hibernate OGM!
Regarding ids, it should work for you if they are mapped using the IDENTITY
strategy:
@Id
@GeneratedValue(strategy=GenerationType.IDENTITY)
Long id;
This causes the Hibernate ORM engine to read back t
ay 2014 09:32:08 -0500
Subject: Re: [hibernate-dev] question on matrix testing
From: st...@hibernate.org
To: maheshgad...@hotmail.com
Why do you keep dropping hibernate-dev from the recipients?
What I find odd is that Sybase does not support one of the few functions that
the SQL spec explicitly n
On Tue, May 13, 2014 at 10:39 AM, Mahesh Gadgil wrote:
> I am running hibernate tests on SAP SYBASE ASE database currently. I am
> looking to get advice on what the best solution is to these problems.I know
> some tests that could not be run on ASE, have been skipped using
> SkipForDialect annotat
Hi Alex,
thank you very much for the response
>> Iirc we expect no entry, as the softlock should have been removed, right?
The softlock is actually not removed when using read-write strategy.
I did implement the delete handling of natural-id analog to the way it is for
entities, where the proce
Hey Günther,
I think your patch there makes sense. I will have a closer look though.
Iirc we expect no entry, as the softlock should have been removed, right? I
might be misremembering. I'm not the single author of all this neither. But
I should be able to spend some time on that tomorrow est. curr
ok, I'll get to it later today hopefully
On Tue 13 Mar 2012 12:50:37 PM CDT, Scott Marlow wrote:
> I created HHH-7169 for this.
>
> On 03/13/2012 11:26 AM, Steve Ebersole wrote:
>> Sure we can make a change like that. Like I said, just trying to make
>> sure this deployment setup is not frowned up
I created HHH-7169 for this.
On 03/13/2012 11:26 AM, Steve Ebersole wrote:
> Sure we can make a change like that. Like I said, just trying to make
> sure this deployment setup is not frowned upon by AS.
>
> On Tue 13 Mar 2012 08:43:12 AM CDT, Scott Marlow wrote:
>> I agree that its only a problem
Sure we can make a change like that. Like I said, just trying to make
sure this deployment setup is not frowned upon by AS.
On Tue 13 Mar 2012 08:43:12 AM CDT, Scott Marlow wrote:
> I agree that its only a problem when the JDBC driver is not on the
> server classpath (AS7 has "Global Modules" t
I agree that its only a problem when the JDBC driver is not on the
server classpath (AS7 has "Global Modules" that allows for that as a
last resort option).
I think it is always better to have the JDBC drivers be available
globally. However, it doesn't matter which approach is used for these
from the post, it seems either deploy jdbc driver within war or deploy the
driver as module, hibernate fails to find it
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
On Mar 13, 2012, at 8:51 PM, Steve Ebersole wrote:
> Is it koser to deploy JDBC drivers with an a
Is it koser to deploy JDBC drivers with an app? I thought the general
suggestion was to make them available to the server classpath?
On Tue 13 Mar 2012 06:47:14 AM CDT, Strong Liu wrote:
> I think we should use classloading service to load it
>
> yes, a HHH would be great.
> ---
I think we should use classloading service to load it
yes, a HHH would be great.
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
On Mar 13, 2012, at 8:24 AM, Scott Marlow wrote:
> Should Hibernate 4.x use the AvailableSettings.APP_CLASSLOADER to load
> JDBC driver
we got a hibernate4 compatible fork in hibernate tools eclipse plugin now.
anyone want to contribute
and help make the now three releases that is needed? (3.2-3.5, 3.6 and 4.0?)
output of hibernate tools work with all versions, its only if you do queries or
need something specific
from hibernate
Hi Mr. Andersen,
>>Problem is that it seems 4.1 will cause similar disjunct API
The "Redesigned metamodel" goal, which was planned for 4.1, surely would have
caused lots of disjunct API's again,
but now I saw on the hibernate roadmap, that in meantime the "Redesigned
metamodel" goal has been
JBoss Tools M5 have an experimental version of the eclipse plugins that works
against both 3.6 and 4.0.
We'll get that merged into hibernate tools in the new year.
Problem is that it seems 4.1 will cause similar disjunct API so the problem
is just getting worse to keep up and keep a stable API/a
Max?
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
On Dec 19, 2011, at 8:59 PM, Guenther Demetz wrote:
> Hi Strong Liu,
>
> do you know, when it is planned a Hibernate-Tools release compatible to
> Hibernate-Core 4.0 Final ?
>
> Me and probably many other hibe
On Aug 16, 2011, at 4:26 PM, Sanne Grinovero wrote:
> Hi Scott,
> demanding people to configure a new cache for each application is very
> tricky because of ISPN-658, unless you're referring to creating a
> whole new instance of Infinispan, with a dedicated new CacheManager
> and either starting
>>
>> I could try setting AvailableSettings.CACHE_REGION_PREFIX to the
>> application scoped pu name. That seems to get added to the region name
>> (region would then be: application name + PU jar name + PU name + entity
>> class).
>>
>> Would that be likely to work?
>
> I think so. This is what
On Tue, 2011-08-16 at 10:45 -0400, Scott Marlow wrote:
> On 08/16/2011 10:26 AM, Sanne Grinovero wrote:
> > Hi Scott,
> > demanding people to configure a new cache for each application is very
> > tricky because of ISPN-658, unless you're referring to creating a
> > whole new instance of Infinispan
2011/8/16 Scott Marlow :
> On 08/16/2011 11:08 AM, Sanne Grinovero wrote:
>>>
>>> I could try setting AvailableSettings.CACHE_REGION_PREFIX to the
>>> application
>>> scoped pu name. That seems to get added to the region name (region would
>>> then be: application name + PU jar name + PU name + en
On 08/16/2011 11:08 AM, Sanne Grinovero wrote:
>> I could try setting AvailableSettings.CACHE_REGION_PREFIX to the application
>> scoped pu name. That seems to get added to the region name (region would
>> then be: application name + PU jar name + PU name + entity class).
>>
>> Would that be likel
> I could try setting AvailableSettings.CACHE_REGION_PREFIX to the application
> scoped pu name. That seems to get added to the region name (region would
> then be: application name + PU jar name + PU name + entity class).
>
> Would that be likely to work?
That sounds like a good plan
__
On 08/16/2011 10:26 AM, Sanne Grinovero wrote:
> Hi Scott,
> demanding people to configure a new cache for each application is very
> tricky because of ISPN-658, unless you're referring to creating a
> whole new instance of Infinispan, with a dedicated new CacheManager
> and either starting a new J
Hi Scott,
demanding people to configure a new cache for each application is very
tricky because of ISPN-658, unless you're referring to creating a
whole new instance of Infinispan, with a dedicated new CacheManager
and either starting a new JGroups channel or using the JGroups
multiplexer Paul had
FYI, I asked a general question on seam-dev about Seam 2.x support for
Hibernate 4.0. Just to get a sense for what is on their radar map (or
not). I got a few questions about running Seam 2 on AS7 in the past few
days and wanted to learn more. :)
On 06/08/2011 07:27 AM, Emmanuel Bernard wrot
On 7 juin 2011, at 21:58, Sanne Grinovero wrote:
> I agree that we should not include it, but are there viable
> alternatives to deploy a Seam2 application?
People would need to embed the lib in their apps.
>
> Also given the nice classloader isolation AS7 provides, if we really
> need to have
I agree that we should not include it, but are there viable
alternatives to deploy a Seam2 application?
Also given the nice classloader isolation AS7 provides, if we really
need to have it around we could hide it from non intentional usage by
not exposing it.
Also in case would it need to work wi
+1 for not including the legacy version. BV and HV 4 are out for 1,5
years now and having the old version around just increases the risk
that someone is using it accidentally (once there was a related
question in the HV feedback forum). And I guess if someone really
needs the old version they could
No it should not. People need to migrate to Hibernate Validator 4 and Bean
Validation now.
On 7 juin 2011, at 15:29, Scott Marlow wrote:
> As 7.0 is not currently including the hibernate-validator-legacy.jar but
> people are asking me if we should include it.
>
> hibernate-validator-legacy.jar
On Tue, 07 Jun 2011 15:29:39 +0200, Scott Marlow
wrote:
> As 7.0 is not currently including the hibernate-validator-legacy.jar but
> people are asking me if we should include it.
>
> hibernate-validator-legacy.jar was included in previous AS releases (see
> JBAS-7608) to help with running Seam
The cglib support in Hibernate has been deprecated since 3.5 or 3.6 and will
be removed in 4.0
On Sunday, March 13, 2011, at 10:38 am, Scott Marlow wrote:
> Hi,
>
> I'm looking at integrating Hibernate JPA persistence provider with AS7.
> On the AS7 IRC channel recently, I was asked to ask abo
The right place for those questions is http://forum.hibernate.org
To answer your question, you have different DBs, so different
SessionFactory configurations (using the same mapping I imagine).
You will just have to change the following property in each
hibernate.cfg.xml
hibernate.search.de
Hello Aleksander,
I've been in a similar situation having to decide between Compass, direct Lucene
and Hibernate Search. I ended up using Hibernate Search because we use
Hibernate and I am very satisfied now, after a year of experience.
About your specific question, I'm not sure I understood your s
ask in forum.
-max
>
>
> Hello to all,
> I am practicing with Hibernate and I have a problem with the management of
> the caching. Excuse my ignorance.
> The simple program that I have developed in order to try the caching's
> functionality gives me
> an output that I can't understand. The prob
Hi,
There is a small patch in JIRA (HHH-2440) that allows the user to
specify that the generated SQL should not contain the distinct keyword.
Mike.
Steve Ebersole wrote:
The in-memory distincting is actually a temporary solution. There are a
few JIRA cases making up the ultimate solution.
You are wondering why a DISTINCT you put into your query is actually
send to the database in the generated SQL?
Yes, or more specifically, why DISTINCT is sent to the database in cases
where result set will be the same with or without the DISTINCT clause.
___
JIRA is searchable. Look for things marked as 'query-hql' as the
component... The basic idea is to drop the collection-valued fetches.
Is this where you will fetch collections in a sub-select rather than a join?
Regards,
Michael Barker.
___
hiberna
Could you point me to the JIRA tasks, I would be interesting in seeing
what the ultimate solution looks like?
JIRA is searchable. Look for things marked as 'query-hql' as the
component... The basic idea is to drop the collection-valued fetches.
The thing that confuses me is that distinct gene
On Feb 19, 2007, at 3:32 PM, Michael Barker wrote:
However I have noticed that everytime distinct is specifed in the
ejb-ql query it also gets specified in the sql query. I am
curious as the reasoning behind this.
You are wondering why a DISTINCT you put into your query is actually
send
Thanks Steve,
Could you point me to the JIRA tasks, I would be interesting in seeing
what the ultimate solution looks like?
The thing that confuses me is that distinct generally doesn't come for
free (generally resuls in a sort by the DB). If the result set is going
to be the same anyway, i
The in-memory distincting is actually a temporary solution. There are a
few JIRA cases making up the ultimate solution.
But specifically to your questions, the DISTINCT applied to the query is
intended to limit the data transferred by the JDBC driver from server to
client, especially on large
67 matches
Mail list logo
