Fully qualified entity name for naming tables

saverio · **Joined:** Tue Feb 20, 2007 12:37 pm **Posts:** 4

I'm trying to write a good (for me) naming strategy, but I'd like to use the name of the packages involved in the class, to make a table. For instance, the entity com.example.project.entities.exampledata shoud make a table named PROJ_ENTI_EXAMPLEDATA or something similar, from now it's just string manipulation.

The problem is that the NamingStrategy classes only get the unqualified class name to work with, so there is no way I con do it just configuring a custom NamingStrategy class.

I found that the only place to change would be in org.hibernate.cfg.annotations.EntityBinder, line 353 (version 3.2.1.GA of hibernate-annotations), in function getClassTableName, where

Code:

return mappings.getNamingStrategy().classToTableName( name );

can be changed to

Code:

return mappings.getNamingStrategy().classToTableName( annotatedClass.getName() );

to do the trick.

But that would be hacking the code, instead I just want to override the code in EntityBinder, and configure the server to use my custom binder.

Any idea about how and where to configure the binder???

Thank you for taking the time to read!

Saverio

andydale · **Posted:** Tue Feb 20, 2007 1:15 pm

I assume you do not want to do this in a static/hardcoded way, but if you did you could annotate your Entities with:

Code:

@Table(name="<your table name>")

Cheers,

Andy

saverio · **Joined:** Tue Feb 20, 2007 12:37 pm **Posts:** 4

:)

Of course, when you have a couple of entities, this should be a good strategy. Now imagine a large project with hundreds of entities, and just in that moment of development when the packages are changing constantly depending on your boss's good will.... !!!refactoring hell!!!

I am hoping for a solution that can stand the attack of the evil refactorer! That is, no explicit naming AT ALL.

emmanuel · **Posted:** Tue Feb 20, 2007 8:13 pm

Can you open a JIRA issue, I can't really do it in a 3.2.x series, but I can slip it in 3.3

saverio · **Joined:** Tue Feb 20, 2007 12:37 pm **Posts:** 4

Thanks Emmanuel for the quick answer. It's good to know that we have reached the actual limits of the software instead of the limits of our vision. I'll try to post it to JIRA as soon as possible. Also it's good that this issue has deserved an archangel's answer in the earliest place!!! It's just like when in the faculty the big guy at the other side of the room says "Good question!".

On the other side, when is the new release (3.3) supposed to exist? That is, if there is a timespan of few (4 or 5) months, maybe I'll wait for the new version to deploy the database, if more, then I'll look for another way (either simple prefixing via NamingStrategy or explicit naming of every table via XML).

Best regards.

Saverio

saverio · **Joined:** Tue Feb 20, 2007 12:37 pm **Posts:** 4

Issue opened:

http://opensource.atlassian.com/projects/hibernate/browse/ANN-561

I hope that someone will soon take on the coding!

Good work to everyone!

Saverio