Hi Sanne,
Thanks for your feedback. I was pretty sure I hadn't all the history!
Getting Google to prioritize our latest doc is probably a long time goal.
I played a bit with jQuery to suggest to the user to go to the latest
stable. Note that I only took into consideration the page for the time
b
Hi Sanne,
Thanks for your feedback. I was pretty sure I hadn't all the history!
Getting Google to prioritize our latest doc is probably a long time goal.
I played a bit with jQuery to suggest to the user to go to the latest
stable. Note that I only took into consideration the page for the time
b
On 19 July 2016 at 18:14, Emmanuel Bernard wrote:
> Assuming we switch to the new mapping approach by default in 6.
> Is there a way via mapping to use the old approach? Or would that
> require some new annotation?
>
> I understand the evolution arguments but frankly in a plain mongodb
> document,
Assuming we switch to the new mapping approach by default in 6.
Is there a way via mapping to use the old approach? Or would that
require some new annotation?
I understand the evolution arguments but frankly in a plain mongodb
document, I would have skipped the single property name. It's forced
up
Hi Guillaume,
yes I'm aware of the issue; we discussed it before, I think on this
same mailing list but maybe it was during our last meeting.
We really need to fix that metadata; Stefania (my partner) is an SEO
consultant and is shocked at how bad we do with this; apparently we
are a funny exampl
Hi,
When we search for Hibernate/Hibernate Search issues, Google send
people to *very* outdated docs.
For instance, searching for %1$s gets me to %2$s:
- hibernate collection element ->
https://docs.jboss.org/hibernate/orm/3.3/reference/en/html/collections.html
(yes, *3.3*)
- hibernate search fac
