Gavin King
Gavin King
So this is something I would be prepared to work on and write up a proposal for, iff: - there's a consensus among current JPA implementers that this is something...
> this is necessary! I mean that's just not true. `@AttributeOverride` is more powerful/flexible, though more verbose. So, while I can see it's perhaps desirable in some cases, it's never...
Look, AFAIK, no existing JPA implementation offers this. There's a rather high bar for adding a feature to JPA when no existing ORM implements that feature. It's not an impossible...
I'm really not a fan of this idea at all. The given code examples are kind of a dog's breakfast of an expression language embedded via `{...}` quotes in a...
I propose we close this.
> I propose we close this. Please someone speak up if you think I should not! :-)
The Hibernate team doesn't recommend the use of `hibernate.globally_quoted_identifiers` so I agree that JPA should not add anything like that.
It's a hard call, and I'm not sure what the spec should say. It's pretty hard for the spec to demand that the implementations auto-quote every single keyword on every...
Alright, so the thing I forgot about is case-sensitivity. Quoting identifiers makes them case-sensitive, which can cause problems since, when the column name is inferred from a Java field name,...
@lukasj Yeah, I think what you just said is about right. OTOH, I'm skeptical that adding such optional settings to the spec is of much value, especially if we can't...