-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: NamingStrategy not used for table name specified w/ @Column
PostPosted: Tue Feb 11, 2014 12:39 pm 
Newbie

Joined: Mon Oct 18, 2010 10:02 am
Posts: 3
We have a need to modify our table names based on a system property, this allows us to run multiple instance against the same
database server for testing.

We implemented a NamingStrategy that overrode the
public String tableName(String tableName)
method to perform the modification.

This worked great until we need to specify the table name in an @Column annotation because the entity used a secondary table.
It looked like the value of the table field for the @Column annotaiton is not run through the NamingStrategy so the name did not match any of the
tables for the entity.

It looks like several other annotations such as @JoinColumn have similiar issues.

Any recommendations on how to proceded would be appreciated.

Thanks,
Mark


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.