This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Multiple Tables In the Database -- Use Multiple Entity Beans?

JiaPei Jen
Ranch Hand
Posts: 1309
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This question is similar to what Chandra Pay asked earlier.
There are multiple tables in my database (The database is structured by someone and given to me). Each table has a primary key, and the table that relates to other tables has a foreign key. I have an entity bean for each table, and I use the primary key and foreign key matching to go from one table to another. The specifics are spelled out below:
There are three tables in the database. The first table has login, pwd, and a primary key as fields, the second table contains completely different fields plus a primary key and a foreign key. The fields in the third table are different from those in the first and second tables plus its primary key. Queries to the third table can be made only if the user login and pwd are found in the first table, and through the third table's relation to the second table. I have three entity beans for each table and am using the container-managed persistence.
The fields in the third table may be accessed concurrently, but those fields are primarily read-only (not updated frequently). My question is if this is a good design and a correct approach? Or I should ask the data person to restructure the database?
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic