Gavin King

> I think this would be a good addition. But if not already a separate request, I suggest we consider how this plays with update/insert handling. I assume the intention...

@AleksNo > I think about something like that: > > public static volatile SingularAttribute myField = new SingularAttributeImpl("myField"); This would be nice, but it's not so simple. There's more information...

I don't see how this proposal makes sense. - We don't support joins to *tables* in HQL, and it's entirely unclear what the semantics of that would be. We support...

This issue has no votes. I believe that no JPA implementations support it. And I don't believe it makes sense to mix native SQL and JPQL in this fashion. Closing.

Either this issue or #230 should be closed.

I don't quite understand what is being requested by this issue: naïvely it seems to me that this is a concern of the CDI spec, and is indeed already required....

I believe that, even if this wasn't covered before, it's now covered by #460, which lets you specify a CDI scope for an injectable `EntityManager` (so you could use `@ConversationScoped`...

@scottmarlow Right, I understand that. But if you can define a CDI bean of type `EntityManager` with scope `@Dependent`, then that's already an "extended persistence context" with the same semantics...

Good point. `@Dependent` would not give you inheritance, but `@ConversationScoped` would give you something a bit better.

So I wondered whether it's possible to define some sort of pseudo-scope which implements the semantics of PC inheritance in CDI, but I don't believe it is. With SFSB, you...