Hi,
Imagine the following situation. I've got two tables in my DB: shops
and products. For each of them I've created seperate DAO (Date Access
Object), so I could ask such question: what is the name of shop X or
add new product. By the given table are connected via relation:
shop-sells-product. So there is a need to build yet another DAO for
cross-table queries, isn't?
What is a good, common-used practice for such situations?
Regards,
Maciej
Manish Pandit - 10 Oct 2006 17:10 GMT
Hi,
You do not need another DAO. This is a bidirectional one to many
relationship, so you can have a collection in both classes. Shops can
contain a Collection or Products, and Product can contain a Collection
of Shops where it is sold.
-cheers,
Manish