Hi,
It seems like a good step to tackle the SEO optimization problem is to
offer a "curent" link in our site to point to the latest docs.
That's how PostgreSQL and Spring do it and once this link is indexed by
google, it will always render the latest version of the docs:
http://www.postgresql.org
Ok, I am going to apply SQM-28-2 upstream.
On Thu, Dec 3, 2015 at 10:36 AM Steve Ebersole wrote:
> I mean that getting information out of them is not easy. Especially
> EntityPersister - specifically getting sub/super information, attribute
> information, etc.
>
>
> On Thu, Dec 3, 2015 at 10:30
Per the discussion Luis and I had on IRC we will go with the prefix
"hibernate.enhancer..". "enhancer" makes it more than clear what the
intended target is.
On Fri, Dec 4, 2015 at 4:50 AM Sanne Grinovero wrote:
> Hi Luis,
> thanks for this proposal, I was looking forward to see more
> improvem
I think that document only landed on 5.1 because lazy groups is 5.1 only.
Docs for 5.0 (and these are just on how to use the build-time plugins)
are in a different place:
documentation/src/main/asciidoc/topical/bytecode/BytecodeEnhancement.adoc
On 12/04/2015 12:58 PM, Steve Ebersole wrote:
> Lu
Thanks Vlad,
Hope you have a great weekend too.
Andrea
On 4 December 2015 at 14:26, Vlad Mihalcea wrote:
> Hi,
>
> I managed to migrate the whole User Guide to AsciiDoctor and you can check
> it out on this branch:
>
> https://github.com/vladmihalcea/hibernate-orm/tree/feature/asciidocs
>
> Ne
Hi,
I managed to migrate the whole User Guide to AsciiDoctor and you can check
it out on this branch:
https://github.com/vladmihalcea/hibernate-orm/tree/feature/asciidocs
Next week, I'll start reading and reviewing it, and make a plan of what
needs to be written so we have a full 5.0 user refere
Luis, I am trying to remember if there is any reason I only added this to
master (5.1). Was there a reason to not add it to 5.0 as well? Aside from
the parts about lazy groups that is :)
On Fri, Dec 4, 2015 at 6:28 AM Steve Ebersole wrote:
> On Fri, Dec 4, 2015 at 5:43 AM Steve Ebersole wrot
On 4 December 2015 at 12:32, Vlad Mihalcea wrote:
> I investigated this issue:
>
> On master it's all fine:
>
>
>
>
>
>
>
>
> but the 5.0.5 tag didn't declare the Bytecode chapter:
>
>
>
>
>
>
>
>
> Vlad
That's great, thanks! Now I might play with it too :)
Sa
Gytis,
When you say
> get Neo4j transaction id in OGM?
what does that exactly mean? Would you like to access it from
application code? What is the use case for accessing it?
Thanks,
--Gunnar
2015-12-04 13:35 GMT+01:00 Davide D'Alto :
> Hi Gytis,
>
> I've sent a pull request for Neo4j remote
Hi Gytis,
I've sent a pull request for Neo4j remote some time ago:
https://github.com/hibernate/hibernate-ogm/pull/596
This is an initial prototype and it still requires some work.
That said, I think you will be able to obtain the transaction id via the
TransactionCoordinator:
TransactionDriver
I investigated this issue:
On master it's all fine:
but the 5.0.5 tag didn't declare the Bytecode chapter:
Vlad
On Fri, Dec 4, 2015 at 1:43 PM, Steve Ebersole wrote:
> On Fri, Dec 4, 2015 at 4:50 AM Sanne Grinovero
> wrote:
>
> > Hi Luis,
> > thanks for
On Fri, Dec 4, 2015 at 5:43 AM Steve Ebersole wrote:
> Hm, there is a problem in the doc generation apparently :( For some
> reason this chapter is not pulled in
> https://github.com/hibernate/hibernate-orm/blob/master/documentation/src/main/docbook/userGuide/en-US/chapters/enhancement/BytecodeE
This all sounds good to me. For runtime enhancement I am ok with
deprecating that setting, as long as in the meantime until its removal we
continue to treat it as enabling all the enhancement features in addition
to logging that warning.
On Fri, Dec 4, 2015 at 12:29 AM Luis Barreiro wrote:
> Hi
On Fri, Dec 4, 2015 at 4:50 AM Sanne Grinovero wrote:
> Hi Luis,
> thanks for this proposal, I was looking forward to see more
> improvements in the area.
>
> Adding more properties sounds good to me, although I'd not use the
> prefix "hibernate.enhance" as it sounds like it's about enhancing
> H
Hi Luis,
thanks for this proposal, I was looking forward to see more
improvements in the area.
Adding more properties sounds good to me, although I'd not use the
prefix "hibernate.enhance" as it sounds like it's about enhancing
Hibernate - which might be true but one could say the same with many
o
I like the idea of having multiple properties to enable a particular
bytecode enhancement feature.
It could be that the clients want to speed-up dirty checking but they don't
really use the lazy initialization.
Vlad
On Fri, Dec 4, 2015 at 8:29 AM, Luis Barreiro wrote:
> Hi all,
>
> I would like
16 matches
Mail list logo