Hi Gail,
I'm glad you like the new User Guide.
Related to the old one, I think we could leave it hosted on docs.jboss.org
because some users might have bookmarked it, and deleting it might get them
angry.
Vlad
On Wed, Apr 6, 2016 at 1:36 AM, Gail Badner wrote:
> Hi Vlad,
>
> I've pushed the d
Hi Vlad,
I've pushed the documentation to
http://docs.jboss.org/hibernate/orm/5.0/userguide/html_single/Hibernate_User_Guide.html
and updated the link on hibernate.org.
The old user guide is still out there. I've asked for it to be removed.
The new user guide looks great! Thanks for your help on
That's exactly what I mean too. I think we can improve it a little bit when
the evict is forced while being on running Session.
But that's not in the scope of the original issue which stays as is.
I'll add a new Jira issue with a test case, and a design change proposal
that we can discuss when we
Thanks for the feedback,
Fo the moment, the 5.0 docs are ready, and we can push the integration
further, as you suggested.
There will be other updates that we'll do to improve the docs (Envers,
Spatial, Portability topics), and I'll make sure to split the 5.1-related
things from changes that appl
The contract for SessionFactory-level even says that it operates outside of
the confines of an Session-based locking of the cached data. So it works
this way by design. We can question the design decision, but that's a
different discussion.
On Tue, Apr 5, 2016 at 9:38 AM Vlad Mihalcea
wrote:
>
Hi Vlad,
It looks great! If it's ready to go, I'll push it to
https://docs.jboss.org/hibernate/orm/5.0/ and update the link on
hibernate.org.
Thanks!
Gail
On Mon, Apr 4, 2016 at 10:47 PM, Vlad Mihalcea
wrote:
> Hi Gail,
>
> I removed the 5.1 references on the new User Guide.
> You can check it
{UÒÙà`EiQ£KðÊR
o~Ë2®B¢þ]UÎeb¯¨
1¯º[ðUÁùTp{0:ózã,bmf¼Q ]ÑE
3±4©ÄY,Oöb[Êè±ì±Æd:§jKûÇõ6lDh;)ÃN?µD>EóU
CUôðÞeÙÛÛ£`¾K91æ
DUr¶ùöLö6{OæÁÁ2· 1Dø%¾Ü3>ÖH(zÑi
«E^äOëa»
O´h±«¹§Z¤Î' Ydq0£ÀDäÁUüØÐÚº¯t
:Gå(Ñï$Ѳ]¥6àj
íûéwKì¬Ã£RàÓTQ"v²ÃrV{iÝ-$ÑX¸H{ÔH¨éQ²ÞéIDåî>}q缤î7|³7?Pyæ
Hi,
I'd definitely fix it for the refresh operation, which does an implicit
cache eviction too.
In this case, the proposed PR solution is fine since it simply locks the
entry right after it is evicted from the cache and releases the lock after
the transaction is ended.
This way, we won't push an u
On 5 April 2016 at 14:11, Vlad Mihalcea wrote:
> Hi,
>
> While reviewing the PR for this issue:
>
> https://hibernate.atlassian.net/browse/HHH-10649
>
> I realized that the ReadWrite cache concurrency strategy has a flaw that
> permits "read uncommitted" anomalies.
> The RW cache concurrency strat
Hi,
While reviewing the PR for this issue:
https://hibernate.atlassian.net/browse/HHH-10649
I realized that the ReadWrite cache concurrency strategy has a flaw that
permits "read uncommitted" anomalies.
The RW cache concurrency strategy guards any modifications with Lock
entries, as explained in
On 5 April 2016 at 07:30, Gunnar Morling wrote:
> Apart from migration concerns, is anything in Lucene 6 allowing us to
> provide new exciting functionality to users?
The best one seems to be the new encoding technique for numerics -
also mentioned as breaking API - is fabulously more efficient:
11 matches
Mail list logo
