They do not. HBM, e.g., uses "idx" for map keys columns as well as
list/array index columns. JPA says to use {attribute-name}_ORDER for list
index column. Unless I missed it (which is completely possible in
annotation binding) we always use the JPA-defined default in those cases
rather than using any *implicit* naming hooks.
So that is really the question. Do we want expand the breadth of what is
covered by implicit naming strategy in this new model? I think its
reasonable.
On Mon, Feb 2, 2015 at 11:28 AM, Emmanuel Bernard <emman...@hibernate.org>
wrote:
>
> On 02 Feb 2015, at 17:51, Steve Ebersole <st...@hibernate.org> wrote:
>
> On Mon, Feb 2, 2015 at 8:34 AM, Emmanuel Bernard <emman...@hibernate.org>
> wrote:
>
> I think you’re missing things like @MapKeyColumn, @OrderColumn
>>
>
> So that's a good discussion. These are things that have previously been
> hard-coded defaults (at least on hbm side) and therefore had no specific
> naming strategy hooks. I'm all for being specific, so if everyone agrees
> it is a good idea to add methods for stuff like this, I am fine with that.
>
>
> I know JPA has well defined values for these. I am not sure they match
> 100% the HBM version.
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
