When I create an application, two tables have to be updated.
I have two tables with the columns given below.
AP_ID -> PK (I use the APP_SEQ to get the next sequence id) INITIAL_SUB_ID ->(This will be the PK of SUBMISSIONS Table. When I create the APPLICATION, I use SUB_SEQ to get the next sequnce id and insert a record into both APPLICATIONS and SUBMISSIONS Table) APP_NUMBER etc..
SUB_ID->PK APP_ID->FK(Primary key of APPLICATIONS Table) SUB_TITLE Etc..
1. When I create the application, I will be updating both APPLICATIONS, SUBMISSIONS Table(Currently I have a view which updates both the tables.) 2. When I create the submission, I will be updating only submissions table as the submission can be created for any of the existing application.
Question: I am planning to replace JDBC with Hibernate. I would appreciate, If any body can help/throw a suggetion for creating mapping file in the above scenario.
Not sure what the initial sub id in Application is for. If it is just which was the first Submission record added, then make that a OneToOne mapping. In regards to the Submission having Many records to One Application sounds like a OneToMany/ManyToOne relationship.
Check out the Hibernate documentation at www.hibernate.org for exact mapping details.
I don't see the use of Initial Submisson Id being present in Applications table. Any way, The database was created 7 years ago and still we are using the same schema.
Coming back to the mapping, I think as you suggested, I need to more read on One to Many or Many to One mappings as The application can have multiple submissions/Multiple submissions can be created for a single application.