Sisäänkirjautuminen| Uusi tunnus
FrontPage| Projects| Forums| Search|
^ DaoGen Forums: › Why? › PHP5? › Using ToString() with PHP › Next DaoGen version almost ready! › Create (insert) and Save (update) PHP examples › Support for numeric object types almost ready! › DaoGen 2.1.0 released! › Compliments and minor suggestion › variables within a class › Foreign key constraint in create() › Security issue!!! › auto-generated columns and create method › Oracle BLOB » DAO for cross-table queries › Please help me.. › Please use this forum for DaoGen related stuff › Call-time Pass-By-Reference › DaoGen 2.4.0 has been released! › How can I show relationships? › DaoGen & PHP 5 › PHP4 vs PHP5 and other considerations. › singleQuery example in php › Why are save and delete not synchronized? › Why are save and delete not synchronized? › DTD for generated XML › DaoGen 2.2.2 has been released! › DaoGen 2.0.2 is available. › For a thesis ?? › Extremely good idea ?? how can I ???? › Usability suggestions for DaoGen › Performance of DaoGen with Mapping tools › Performance with List › Some usage statistics › DaoGen 2.2.1 has been released! › Programming Examples are back! › DaoGen 2.0.1 is available. › Version 2.0.0 generates buggy PHP code! New version soon available! › Examples of DaoGen customizations › Code Examples
Sisäänkirjautuminen
» Käyttäjätunnus:
» Salasana:
» Muista kirjautuminen:
Suosituimmat sivut: › DaoGen Forums › Programming Examples › DaoGen FAQ › Using ToString() with PHP › DaoGen Manual › DaoGen 2.1.0 released! › Forums › Projects › Create (insert) and Save (update) PHP examples › Search
FrontPage » Forums » DaoGen Forums » DAO for cross-table queries

DAO for cross-table queries

Posted by anonymous 10.10.2006 16:07

Hi,

This general problem with design patterns, but I suppose you're experienced with similar problems. 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