Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-1850

Dynamic runtime @Table name configuration


    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: usability
    • Labels:
    • Environment:
      All environments


      I'm wondering if there is a way to map multiple tables who's name won't be known until runtime to a single entity class. More specifically, My application uses a single entity which it knows the schema for, but not the table name until runtime. The applications has to read the table name from another know table after startup. All there is at deployment is the key into that table. The application consists of a farm of identical apps all running different configurations. They basically store data from different JMS queues to the database.

      I can't find anything useful about this except some byte code manipulators which don't seem to work on the annotation since it appears that the class is already loaded.

      I think there is a legitimate need for such an enhancement. I often have run into sqlServer users who don't know how to use segmented clustered indexing or can't install an Enterprise version so don't have access to this. They create multiple tables and use prepared statements.
      This would enable other cheap dbms to be used without having to worry about locking and contention at the table level.

      Does anyone have any opinions on this?




            • Assignee:
              hughbragg Hugh
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: