I finally have a working solution which allows me to move on with the
upgrade of Hibernate Search, yet the solution in the Search testsuite
is essentially sweeping the problem "under the carpet".
I'm taking it as it allows me to move out of stale-mate (and it's not
a Search problem) but opened an
Hi,
it seems that when using Collection of elements in MongoDB, users
expect to have the elements in the same order as in the db. You can
see the question on the forum here:
https://forum.hibernate.org/viewtopic.php?f=31&t=1043903&p=2491218#p2491218
I also found this StackOverflow question:
http:/
I think it's a reasonable expectation, as long as we're talking
specifically about mapping a *List* and not just a generic Collection.
On 13 January 2017 at 12:18, Davide D'Alto wrote:
> Hi,
> it seems that when using Collection of elements in MongoDB, users
> expect to have the elements in the s
>
> I think it's a reasonable expectation, as long as we're talking
> specifically about mapping a *List* and not just a generic Collection.
>
Ah, this topic again :) I know I'll be all lone, but I'll try anyway!
If we do it for List, and unless there are technical issues that prevent us
from doi
Hi Yoann,
while you might be using a specific implementation when persisting
your new entities, when you're loading the object back from the
database how is Hibernate supposed to know
A) which implementation you want it to use
B) which order to use, if you didn't map e.g. an order column to
stor
I've created a JIRA for this https://hibernate.atlassian.net/browse/OGM-1236
Thanks
On Fri, Jan 13, 2017 at 2:26 PM, Sanne Grinovero wrote:
> Hi Yoann,
>
> while you might be using a specific implementation when persisting
> your new entities, when you're loading the object back from the
> datab
Hi Sanne,
> while you might be using a specific implementation when persisting
> your new entities, when you're loading the object back from the
> database how is Hibernate supposed to know
> A) which implementation you want it to use
Ok, that's true for most collection interfaces, but I'm not
On 13 January 2017 at 15:30, Yoann Rodiere wrote:
> Hi Sanne,
>
>>
>> while you might be using a specific implementation when persisting
>> your new entities, when you're loading the object back from the
>> database how is Hibernate supposed to know
>> A) which implementation you want it to use
>
>
> I'm a bit lost here. If you don't want to expose an "unnecessary
> promise" like ordering, why would you need OGM to maintain ordering?
As explained below:
> You could add documentation on a getter stating what the expected ordering
> is (and, frankly, it may be relevant even with a List: ho
