I do wonder if OperationContextType should not be integrated into
EventType. I hate repeatng this set of enumerations. Something like
https://gist.github.com/sebersole/2a4af882d0a61696dce39d242023add0
Not specific to this PoC but one thing I would also like to see is the
ability to know the Even
Hi Steve,
I can start integrating this code into your wip/6.0 branch. Are there any
fundamental changes you would like to see before I integrate, or should I
integrate as is?
Thanks,
Gail
On Fri, Apr 1, 2016 at 12:14 PM, Steve Ebersole wrote:
> I do like the proposal. Awesome job on the gist.
I do like the proposal. Awesome job on the gist. I'll look over the code
over the next few days.
On Thu, Mar 31, 2016 at 3:05 PM Gail Badner wrote:
> Replying for consideration for 6.0.
>
> On Mon, Feb 8, 2016 at 6:12 AM, Steve Ebersole
> wrote:
>
>> This is going to have to wait post-5.1 as
Replying for consideration for 6.0.
On Mon, Feb 8, 2016 at 6:12 AM, Steve Ebersole wrote:
> This is going to have to wait post-5.1 as I mentioned earlier if this was
> not ready prior to last week.
>
> I have just too much on my plate to look at this over 2 days.
>
> On Mon, Feb 8, 2016 at 12:29
This is going to have to wait post-5.1 as I mentioned earlier if this was
not ready prior to last week.
I have just too much on my plate to look at this over 2 days.
On Mon, Feb 8, 2016 at 12:29 AM Gail Badner wrote:
> The POC [1] assumes that we only need a single OperationContext for each
> t
The POC [1] assumes that we only need a single OperationContext for each
type of operation. OperationContextManager has a Map of OperationContext by
OperationContextType. Each OperationContext object is lazily created on the
first occurence of the corresponding type of operation.
Currently, when a
I've created a gist with an overview of the design:
https://gist.github.com/gbadner/f0e635e8fba7b84af233 . I will add a new
section tomorrow about possible shortcomings.
Here is my POC:
https://github.com/hibernate/hibernate-orm/compare/master...gbadner:HHH-10478-OperationContext
. Although no tes
