| Author |
DAO for joined tables
|
Cj Recto
Greenhorn
Joined: Mar 02, 2012
Posts: 25
|
|
hellow guys, I'm currently on learning using Dao pattern in my project. So as what I know, one Table is equivalent to one DAO, am I right? just like StudentDao, SubjectDao. Each dao performs crud operations in their associated tables. But my question is , how am I going to create a DAO for joined tables? lets say I have a query to join student and subject table, then how do I create a DAO for that? Should I place it to the StudentDao? or to SubjectDao? or there's a good practice in that kind of situation?
TIA!
|
 |
Palak Mathur
Ranch Hand
Joined: Jan 29, 2007
Posts: 303
|
|
|
I think you may want to read http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html. If you still have more doubts than let us know.
|
Palak Mathur | My Blog | TechJaunt | What is JavaRanch? | List of All FAQs
|
 |
rambabu desina
Ranch Hand
Joined: May 26, 2012
Posts: 32
|
|
thanks for your help
and i have read that article but i have understood DAO design pattern but i did not get any help for DAO class for joined tables
please give me some more explanation
|
 |
myyron latorilla
Greenhorn
Joined: Dec 10, 2009
Posts: 26
|
|
|
my take is it is really upto you on where to put such method, but you may want to consider cohesion, for example, if you are querying for the name of students that are enrolled to a specific subject then you may want to consider to put that in the SubjectDAO because your result makes sense to be coming from such class than from StudentDAO. Having the method name something like "getStudents(String subject)" will also help you decide. Hope this helps.
|
 |
 |
|
|
subject: DAO for joined tables
|
|
|