feature request, but
>> not a bug. As you mentioned, if you define this enum separately,
>> everything works as expected, right? Is there some reason why that
>> approach can't be done?
>>
>> Kevin
>>
>>
>>
>> On Sat, Jan 4, 2014 at 4:50
Can someone confirm whether or not this is a known issue, or if this is a
known limitation?
When I define an enum as part of my entity class, I am not able to use its
values as literals in a JPQL statement:
package com.myorg.jpa;
public Foo {
public enum FooType { FOO, BAR }
@Enu
hip to a detached RelatedObject. The merge operation isn't
> cascaded by default, so the rules become a little muddy.
>
> Adding CascadeType.MERGE will also solve the problem, is that an
> acceptable
> solution for you?
>
> -mike
>
> On Sun, Jun 19, 2011 at 9:
Since this sounds like a basic operation that fails for me, I'm inclined to
think I'm doing something wrong, but I can't find anything similar in the
FAQ or online, so please tell me what I am missing here.
If I use merge() to insert a new entity that has a many-to-one relationship
to another enti
