- bundler
(both, system wide)
The system-wide ruby version is:
ruby 2.1.6p336 (2015-04-13 revision 50298) [x86_64-linux]
Thanks,
Sanne
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
o add it?
Cheers,
Davide
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Test from new Nabble gateway
--
View this message in context:
http://hibernate-development.74578.x6.nabble.com/Test-from-Nabble-tp3.html
Sent from the Hibernate Development mailing list archive at Nabble.com.
___
hibernate-dev mailing list
hibernate
The timebox for CR2 release is next Wednesday. However I am taking some
time off early next week. As a result I am going to push CR2 back one week.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo
well.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
n
guide as well.
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
tests were significantly faster.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
priority for him (gridtype, mapping,
something else) let us know.
Meeting ended Tue Jul 21 14:13:19 2015 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2015/hibernate-dev.2015-07-21
me) but fail against MariaDB databases.
The other difficulty with a dialect specific for MariaDB is
auto-detection. The MariaDB JDBC drivers report the underlying database as
mysql.
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
without the advanced features.
I wonder if and / or how we should improve that state of affairs.
Emmanuel
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I am feeling like so many changes to SPIs have piled up on master since CR2
that another CR is warranted. Everyone ok with doing a CR3?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Worth keeping these around anymore? They are woefully out of date.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
end I have put together a
> proposal for these changes, it is attached. I'd like to get some
> feedback. Thanks
>
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
for these changes, it is attached. I'd like to get some
> feedback. Thanks
>
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
________
er a
>> proposal for these changes, it is attached. I'd like to get some
>> feedback. Thanks
>>
>> ___________
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/
?)
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
have been putting a lot of TLC into the ORM documentation this weekend
>>> getting ready for 5.0 to go Final. To that end I have put together a
>>> proposal for these changes, it is attached. I'd like to get some
>>>
ect
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
t; to do there prior to Final.
>
>
> On Wed, Jul 29, 2015 at 10:06 AM Steve Ebersole wrote:
>
>> per $subject
>>
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> http
>
>> per $subject
>>
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
to not
>> upload the docs yet since they are still incomplete and i still have work
>> to do there prior to Final.
>>
>>
>> On Wed, Jul 29, 2015 at 10:06 AM Steve Ebersole wrote:
>>
>>> per $subject
>>>
>> ________
to ORM 5.0.0.CR3
>> https://github.com/wildfly/wildfly/pull/7842
>>
>> On 07/29/2015 11:37 AM, Steve Ebersole wrote:
>>> The release is done minus announcing and SF upload. Also I decided to not
>>> upload the docs yet since they are still incomplete and i still
r to Final.
>>
>>
>> On Wed, Jul 29, 2015 at 10:06 AM Steve Ebersole wrote:
>>
>>> per $subject
>>>
>> ___________
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.
em?
>>> On 27 Jul 2015 14:39, "Steve Ebersole" wrote:
>>>
>>>> I have been putting a lot of TLC into the ORM documentation this weekend
>>>> getting ready for 5.0 to go Final. To that end I have put together a
>>>> proposal for
37 AM, Steve Ebersole wrote:
>>> The release is done minus announcing and SF upload. Also I decided to not
>>> upload the docs yet since they are still incomplete and i still have work
>>> to do there prior to Final.
>>>
>>>
>>> On Wed, Jul 29,
gt; https://github.com/wildfly/wildfly/pull/7842
>>>
>>> On 07/29/2015 11:37 AM, Steve Ebersole wrote:
>>>> The release is done minus announcing and SF upload. Also I decided
>>>> to not
>>>> upload the d
/basic/src/test/java/org/jboss/as/test/integration/jpa/secondlevelcache/JPA2LCTestCase.java#L229
>>>>
>>>>
>>>> This hurts my WF10 upgrade to ORM 5.0.0.CR3
>>>> https://github.com/wildfly/wildfly/pull/7842
>>>>
>>>> On 07/29/2
r than BINARY). But really it is useful
for altering any implicit attribute type mapping.
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
here are better alternatives to document.
Thoughts?
[1] - By "soft-deprecate" I mean remove discussion of it from the
documentation, and don't really push it.
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.
question here is whether we want to change this
> (now/ever) to use the JPA (2.0) compliant one?
From a few weeks ago on
https://www.mail-archive.com/hibernate-dev@lists.jboss.org/msg12650.html:
"
Question: Should
hibernate.implicit_naming_strategy=org.hibernate.boot.model.naming.Implicit
o mention Hibernate users would get a more
consistent experience across environments.
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
o others
that are reading this discussion. Your point being that changing either
ORM or WildFly to use the others defaults, brings more consistency
across environments.
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
houghts y'all have.
> >>
> >>
> >> On Mon, Jul 27, 2015 at 2:31 PM Sanne Grinovero
> >> wrote:
> >>
> >>> I didn't receive an attachment. AFAIK the mailing list drops them?
> >>> On 27 Jul 2015 14:39, "Steve
econd email with a link ;)
>> >>
>> >> Anyway.. I just pushed some initial work on the manual. Its not
>> complete
>> >> yet. And I still need to start on the mapping guide. Let me know any
>> >> thoughts y'all have.
>> >>
>> &g
rsion.
Also, auto-quoting keywords (only) is not JPA-compliant.
I would be more comfortable if auto-quoting keywords is considered
experimental, and not the default behavior.
mailman/listinfo/hibernate-dev
> <https://lists.jboss.org/mailman/listinfo/hibernate-dev>
>
______
#x27;d like some valid compelling
arguments for it. Actually for this one I think I am convinced to disable
it by default. But more so because of it being overly aggressive at the
moment. Also, in a way it is nice to make users opt-in to such features.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
matically quote SQL identifiers that are
> keywords... I'll wait... ;) Because it is simply not there. You are
> confusing a problem in the TCK run because of this feature being too
> aggressive at the moment with being compliant or not with the spec.
>
> Again, I am ok changing this default. But I'd like some valid compelling
> arguments for it. Actually for this one I think I am convinced to disable
> it by default. But more so because of it being overly aggressive at the
> moment. Also, in a way it is nice to make users opt-in to such features.
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
g change for applications
>>> that were developed or migrated to an earlier 5.0 version.
>>>
>>> Also, auto-quoting keywords (only) is not JPA-compliant.
>>>
>>
>> As I mentioned above, I am tired of hearing this as an argument for
>> setting defaults :) And here its not even true. Show me where the spec
>> says that a provider cannot automatically quote SQL identifiers that are
>> keywords... I'll wait... ;) Because it is simply not there. You are
>> confusing a problem in the TCK run because of this feature being too
>> aggressive at the moment with being compliant or not with the spec.
>>
>> Again, I am ok changing this default. But I'd like some valid compelling
>> arguments for it. Actually for this one I think I am convinced to disable
>> it by default. But more so because of it being overly aggressive at the
>> moment. Also, in a way it is nice to make users opt-in to such features.
>>
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
viders, but that is
> ultimately the user's choice.
> ___________
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________
h
way to access this in another way?
>
Again, depends on exactly what you hope to accomplish here. Your main
options will be either:
1) grab the org.hibernate.tool.schema.spi.SchemaManagementTool from the
StandardServiceRegistry and use it to obtain the SchemaCreator
and SchemaDropper, passing
; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Hibernate5 migration
There is a migration guide:
https://github.com/hibernate/hibernate-orm/blob/master/working-5.0-migration-guide.md.
It is still a work in progress as in its is not "prettified" yet (as 5.0 is
not final yet.
all
> of them are feasible. I’m leaving out the details here as it would go off
> topic – at the moment I’m just looking for a way to migrate it to H5
> keeping the same functionality we have been using (extract the create/drop
> DDL from a live SF as fast as possible)
>
>
>
> Th
digestible chunks. But that never gained traction. Should they
>>> > just go away?
>>> >
>>> >
>>> > On Mon, Jul 27, 2015 at 5:10 PM Steve Ebersole
>>> wrote:
>>> >
>>> >> Sanne, yep thats why I sent the second email with
27;bothcol.html.haml' defines 'leftcol.html.haml' and
> 'rightcol.html.haml' are defined. But I have no idea if that is the right
> place. I have never even seen a right-hand column in use in the website.
> And I have not found any specific 'leftcol.html.ham
y as another section there. Anyone able to give me some pointers
> how
> > to hook into the left-hand nav links are managed?
> >
> > I see 'bothcol.html.haml' defines 'leftcol.html.haml' and
> > 'rightcol.html.haml' are defined. But I have no idea if that is the
> right
> > place. I have never even seen a right-hand column in use in the website.
> > And I have not found any specific 'leftcol.html.haml' or
> > 'rightcol.html.haml' files.
> >
> > [1] https://hibernate.atlassian.net/browse/WEBSITE-382
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
elation.to and there is also a Dockerfile there
as well now.
--Hardy
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
ts too
late to start something that ambitious tonight. I'll start that in the
morning, unless someone wants to pick that up in the next few hours before
I get back on line.
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.j
porting spatial
queries?
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
?
Cheers,
Davide
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
It's too late and I am too tired to start the release tonight. I'll start
it first thing in am.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
; <https://github.com/hibernate/hibernate-orm/pull/847>
--
Adam Warski
http://twitter.com/#!/adamwarski <http://twitter.com/#!/adamwarski>
http://www.softwaremill.com <http://www.softwaremill.com/>
http://www.warski.org <http://www.warski.org/>
___
s://github.com/hibernate/hibernate-orm/pull/847
>
>
> --
> Adam Warski
>
> http://twitter.com/#!/adamwarski
> http://www.softwaremill.com
> http://www.warski.org
>
>
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
.
> ---
> Public PGP Key at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
> ___
> hibernate-dev mailin
that the subquery is correlated. Hopefully that makes sense, what
I am getting at.
WDYT?
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
e a (build time) transformation
tool based on that code.
[1] - The things that we cannot readily transform is a very small set of
things. Really property-ref is the only thing that comes to mind.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss
).
2. OGM could avoid using the 2lc on WildFly.
Any preferences or suggestions?
Scott
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
). Whether the ForeignKey is generated
> is a whole different story.
> * More aggregation at the binding level. For example, RootClass currently
> exposes multiple pieces of information about an identifier (pk), rather
> than just a single "identifier descriptor". Same for caching descriptor,
> "fetching characteristics", etc.
>
>
> [1] - https://hibernate.atlassian.net/browse/HHH-10213
>
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
just a collection
> of columns (encapsulation). Whether the ForeignKey is generated is a whole
> different story.
> * More aggregation at the binding level. For example, RootClass currently
> exposes multiple pieces of information about an identifier (pk), rather than
> ju
gt; the split between logical and physical naming, and keeping reference to
>> both.
>> * Defining associations based on a ForeignKey, rather than just a
>> collection of columns (encapsulation). Whether the ForeignKey is generated
>> is a whole different story.
>> * More aggregation at the binding level. For example, RootClass
>> currently exposes multiple pieces of information about an identifier (pk),
>> rather than just a single "identifier descriptor". Same for caching
>> descriptor, "fetching characteristics", etc.
>>
>>
>> [1] - https://hibernate.atlassian.net/browse/HHH-10213
>>
>>
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
gt;>>
>>> Some (not exhaustive) specific changes include:
>>> * As mentioned above, I'd really like to rework at least the relational
>>> side. Specifically replace org.hibernate.mapping representations of Table,
>>> Column, Formula, etc with definitions more in line with the definitions we
>>> worked on in metamodel. This includes tables, columns, etc understanding
>>> the split between logical and physical naming, and keeping reference to
>>> both.
>>> * Defining associations based on a ForeignKey, rather than just a
>>> collection of columns (encapsulation). Whether the ForeignKey is generated
>>> is a whole different story.
>>> * More aggregation at the binding level. For example, RootClass
>>> currently exposes multiple pieces of information about an identifier (pk),
>>> rather than just a single "identifier descriptor". Same for caching
>>> descriptor, "fetching characteristics", etc.
>>>
>>>
>>> [1] - https://hibernate.atlassian.net/browse/HHH-10213
>>>
>>>
>>>
>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Specifically replace org.hibernate.mapping representations of Table,
>> Column, Formula, etc with definitions more in line with the definitions we
>> worked on in metamodel. This includes tables, columns, etc understanding
>> the split between logical and physical naming, and keeping reference to both.
>> * Defining associations based on a ForeignKey, rather than just a collection
>> of columns (encapsulation). Whether the ForeignKey is generated is a whole
>> different story.
>> * More aggregation at the binding level. For example, RootClass currently
>> exposes multiple pieces of information about an identifier (pk), rather than
>> just a single "identifier descriptor". Same for caching descriptor,
>> "fetching characteristics", etc.
>>
>>
>> [1] - https://hibernate.atlassian.net/browse/HHH-10213
>> <https://hibernate.atlassian.net/browse/HHH-10213>
>>
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
t; not like it adds work for you tomorrow :)
>>
>> Some (not exhaustive) specific changes include:
>> * As mentioned above, I'd really like to rework at least the relational
>> side. Specifically replace org.hibernate.mapping representations of Table,
>>
helpful, please add your vote to the JIRA:
https://hibernate.atlassian.net/browse/HHH-10216
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
e.mapping). Most of the changes I propose relate to relational
>>>> side. A lot of it deals with aggregating related state (OO design).
>>>>
>>>> Koen, I'd especially like you thoughts as this would represent another
>>>> change that I think affects you in tooling code. This would be work done
>>>> as part of the "jandex-binding" work, which is still to-be-scheduled, so
>>>> it's not like it adds work for you tomorrow :)
>>>>
>>>> Some (not exhaustive) specific changes include:
>>>> * As mentioned above, I'd really like to rework at least the relational
>>>> side. Specifically replace org.hibernate.mapping representations of Table,
>>>> Column, Formula, etc with definitions more in line with the definitions we
>>>> worked on in metamodel. This includes tables, columns, etc understanding
>>>> the split between logical and physical naming, and keeping reference to
>>>> both.
>>>> * Defining associations based on a ForeignKey, rather than just a
>>>> collection of columns (encapsulation). Whether the ForeignKey is generated
>>>> is a whole different story.
>>>> * More aggregation at the binding level. For example, RootClass
>>>> currently exposes multiple pieces of information about an identifier (pk),
>>>> rather than just a single "identifier descriptor". Same for caching
>>>> descriptor, "fetching characteristics", etc.
>>>>
>>>>
>>>> [1] - https://hibernate.atlassian.net/browse/HHH-10213
>>>>
>>>>
>>>>
>>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
DL. This was the fastest solution with the least amount of impact.
>> For the record: I’m aware there are other solutions for this, but not all
>> of them are feasible. I’m leaving out the details here as it would go off
>> topic – at the moment I’m just looking for a way to migrat
his: in some types of test we
> >> actually commit data to our in-memory database. In order to clear the
> >> database between tests, we simply drop and recreate the entire schema
> based
> >> on the DDL. This was the fastest solution with the least amount of
>
d a Jira if you'd like to see them mapped.
I added HHH-9411 for mapping the transaction factory classes.
Thanks,
Scott
>
>
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
week (Nov 18 or Dec 2nd),
and having 5.0.5 4 weeks after that. Votes? Preferences? Silence means I
pick...
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Reference https://hibernate.atlassian.net/browse/HHH-10242
I need to make another change in HCANN and pull that new version into ORM.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
--Gunnar
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
nc in Jira
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
gt;
> Any objections?
> _______
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
ht
ate 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 objections?
>> ___________
>> hibernate-dev mailing list
&g
5 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.
>>>
gt;>>
>>>> The new code is superior and already feature compatible back to 5.0 Final.
>>>>
>>>> Any objections?
>>>> _______
>>>> hibernate-dev mailing list
>>>> hibernate-dev@lists.jboss.org
>>>> https://
n we have your oppinion on it?
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
> ___________
>> (something
>> like activeByDefault=true). Can we have your oppinion on it?
>> --
>> Regards, Petar!
>> Karlovo, Bulgaria.
>> ---
>> Public PGP Key at:
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
>> Key Finger
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 fe
tions
>> >>>
>> >>> On 11 November 2015 at 17:55, Steve Ebersole
>> wrote:
>> >>>
>> >>>> I'd like to more formally deprecate the legacy bytecode enhancement
&
t;>> >> here's a 6-year old issue:
>>> >>
>>> >> https://hibernate.atlassian.net/browse/HHH-3815
>>> >>
>>> >> That suggests to add another attribute on the @Filter annotation
>>> >> (something
>>> >> like activeByDefault=true). Can we h
.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Per $subject
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Per $subject
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
ment' --- the big warning around it is to keep !!!
Regards,
--
Luis Barreiro
JBoss^® by Red Hat
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
too.
Vlad
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
s://issues.apache.org/jira/browse/LUCENE-6917
_______________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
this, but I am just not really sure what would be
required to get it to a point where it would be acceptable for inclusion.
Stuart
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
one of them would be
deprecated moving forward.
Thoughts?
Thanks,
Gail
_______
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Merry Christmas guys and have a great time during the winter holidays.
Vlad
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
me know what you think.
Vlad
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi,
I know that any quoting from a copyrighted material needs written approval.
The JPA specs are under copyright, so instead of quoting we should just
provide the section and
make a summary in our own wording.
Vlad
___
hibernate-dev mailing list
Trying to push and verify my announcement blog post for 5.0.7 release, but
Jenkins fails to build it[1]. Apparently command `rake` not found.
So what now?
[1] - http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/
___
hibernate-dev
Hi,
I think it will be useful to consider adding support for Keyset pagination:
http://use-the-index-luke.com/no-offset
This could be a very strong feature that would set us apart from our
competition.
Vlad
___
hibernate-dev mailing list
hibernate
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
ingle/#caching
> [2]
>
> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#performance-cache
>
> --
> Radim Vansa
> JBoss Performance Team
>
> _______
> hibernate-dev mailing list
> hiberna
gt;
> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#performance-cache
>
> --
> Radim Vansa mailto:rva...@redhat.com>>
> JBoss Performance Team
>
> ___
> hibernate-dev mailing list
> hi
> >
> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#performance-cache
> >
> > --
> > Radim Vansa mailto:rva...@redhat.com>>
> > JBoss Performance Team
> >
> > _
looking in a wrong place?
>> >
>> > Radim
>> >
>> > [1]
>> >
>> http://docs.jboss.org/hibernate/orm/5.0/userGuide/en-US/html_single/#caching
>> > [2]
>> >
>> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single
hibernate/orm/5.0/userGuide/en-US/html_single/#caching
> > [2]
> >
>
> http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#performance-cache
> >
> > --
> > Radim Vansa <mailt
hen I took a look into 5.0 docs [1]
>> there's close to
>> > nothing; is it by purpose? In 4.3 docs [2], there's much
>> more on this
>> > subject. Am I looking in a wrong place?
>> >
>> > Radim
>>
901 - 1000 of 18795 matches
Mail list logo
