Re: [hibernate-dev] Hibernate site SEO optimization

Let's revive this discussion and work on getting a solid plan in place. I think the first question is whether we can get the proper header updates in place in the current doc server. As pointed out, we do not control the root of that machine. Additionally we do not even have our own doc root, me

[hibernate-dev] Eager fetch and duplicates of collection elements

Hi, I understand that $subject is a known source of confusion for people when working with HQL/criteria queries and not applying something like DistinctRootEntityResultTransformer. I am seeing the same behaviour though when getting a root entity by id and join-fetching two (nested) collections. T

Re: [hibernate-dev] Eager fetch and duplicates of collection elements

Hi, True. I also wondered why don't we use the DISTINCT as the default mechanism. While the underlying SQL would return a result-set according to the total number of joined relations, we are building the entity tree hierarchy and I don's see why a user would be interested in getting duplicate root

Re: [hibernate-dev] Eager fetch and duplicates of collection elements

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 > mechanism. > While the underlying

Re: [hibernate-dev] Eager fetch and duplicates of collection elements

Filed bug https://hibernate.atlassian.net/browse/HHH-10519; Reproducer is at https://github.com/gunnarmorling/hibernate-test-case-templates/commit/3c5507755f83039fe40eac7daaa9f1060d97e426. --Gunnar 2016-02-11 15:13 GMT+01:00 Steve Ebersole : > We can make that change in SQM, but its not an opt

[hibernate-dev] documentation translations

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 mo

Re: [hibernate-dev] documentation translations

I think it's nearly impossible to keep documentation to date across several languages. 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

Re: [hibernate-dev] documentation translations

Ok, then I will drop the 'en-US' part from the path. A related discussion about the 'html' versus 'html_single' paths. Currently the asciidoctor outputs are put into the 'html' path, but what goes there is what is normally considered html-single. At the moment Asciidoctor does not offer chunked h

Re: [hibernate-dev] documentation translations

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 distinction? Just 'html' would work for me as well. --Hardy pgp0HN7837BKS.pgp Description: PGP signatu

Re: [hibernate-dev] documentation translations

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 distinction? Just 'html' woul