Change Table Name of an Entity on runtime?

There is this table that is being generated on a monthly basis. Basically the table structure of all monthly tables is the same.

Since it would be a lot of work to map the same entity just with a different table name,

Is it possible to change the table name of an entity as follows on runtime since they have the same table structure after all?

   @Table(name="FOO_JAN2010") // any other ways to generate this dynamically?
   public class FooJan2010Table {  // if we can dynamically set the table name this can be simply named FooTable

If not, what approach can you suggest?


Is it possible to change the table name of an entity as follows on runtime since they have the same table structure after all?

This is not really possible, at least not with standard JPA (which doesn't mean I did it with non standard JPA) as mentioned in questions such as:

To summarize, JPA doesn't offer a way to "alter" a given entity of an already initialized persistence unit (and the related pre-compiled CRUD queries, the pre-compiled named queries, etc).

Still, since you're using Hibernate, maybe have a look at to get an idea of what would be possible using Hibernate Core API.

Another option I can think of would be to use a database synonym / alias: FOO would be an alias for FOO_JAN2010 until... you change the alias to point on FOO_FEB2010. I've never tested this, I don't know if it will suit your needs. But it's another idea.

You can probably do it using Naming Strategies if you use Hibernate as JPA provider. See my answer to this previous question for reference.

You should be able to design your naming strategy to return table names in a dynamic way.

The question whether you should do it that way is a completely different one, though.

Also, thanks Pascal for reminding me, this will only work if the EntityManagerFactory is recreated once per month (there are many ways to do that, restarting the webapp being the simplest one)

I cannot imagine a good way to map this. If this is a legacy database, you'll have a hard time using JPA to access it.

If, however, the database layout is under your control, then I'd change it. Having multiple tables with the exact same layout is usually bad design. You could achieve the same result by having only one table with extra columns for year and month. Don't forget to put an index on the two columns.

I could not figure this one either, had a similar requirement.

Since my table name changed relatively infrequently (daily) , I ended up defining a DB alias to the "active" table at the RDBMS (I am using DB2) and referenced the table alias name in the @Table annotation.

I am fully aware this is not strictly what the OP asked, but thought I would share the experience.

Need Your Help

PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value

android cordova

After typing cordova run android in terminal, I'm getting this error:

any rules of thumb how to smooth FFT spectrum to prevent artifacts when hand-tweaking?

fft frequency dft

I've got a FFT magnitude spectrum and I want to create a filter from it that selectively passes periodic noise sources (e.g. sinewave spurs) and zero's out the frequency bins associated with the ra...