[hibernate-dev] Naming and "naming strategies"

[Emmanuel Bernard]

I’d say +1 for adding coverage of them in the implicit naming strategy.

> On 02 Feb 2015, at 19:16, Steve Ebersole <steve at hibernate.org> wrote:
> 
> 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 <emmanuel at hibernate.org <mailto:emmanuel at hibernate.org>> wrote:
> 
>> On 02 Feb 2015, at 17:51, Steve Ebersole <steve at hibernate.org <mailto:steve at hibernate.org>> wrote:
>> 
>> On Mon, Feb 2, 2015 at 8:34 AM, Emmanuel Bernard <emmanuel at hibernate.org <mailto:emmanuel at 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.
>