[hibernate-dev] document update change?

Sanne Grinovero sanne at hibernate.org
Wed Apr 1 06:49:48 EDT 2015


On 1 April 2015 at 11:39, Ales Justin <ales.justin at gmail.com> wrote:
>> I expect our Update routines to still work. I don't know what the code
>> you're showing does though, as those are not our APIs.
>>
>> If you could share a test using our APIs I'll look at it.
>
> What about if you run our test? :-)
> (it should be easy -- once you have all CD projects checked-out and built)

Sorry I won't have time this week, I'll be on holidays next week, and
then probably have to catch up the week after. If you're happy to wait
a month, ok.

>> The only thing I can think of is that now there's an explicit FLUSH
>> type of Work, if you miss that you might hit stale (deleted) values
>> with a Query.. but this mistake should only be possible if you're
>> driving the backend directly as our public APIs generate them as
>> needed.
>
> Do we need to call this flush explicitly?

Yes

> As I added Thread::sleep(3000) between update and lookup, and it didn't help.

It's event based, not time sensitive.

>
> -Ales
>


More information about the hibernate-dev mailing list