Quote Originally Posted by codezilla
Sounds like you're ready for a Data Access Object (DAO). DAOs are great because you can keep all the SQL necessary for a domain model class isolated in a single DAO class. Generally speaking, you have one DAO class per database table.
I want to understand DAO Patterns. All your examples based on the strategy "one DAO class per database table". I ask me if DAO's can describe complex datastructures, thats mean SQL statements with "join"'s?