The DAO pattern is not that much focused on complexity – it is more a technique to seperate object persistence and data access logic from any given persistance mechanism. That means that the DAO design pattern gives flexibility i.e. if you want to change a database from one type to another.

You can then say that my implementation is a little bit off, since I have SQL-calls directly in my DAO :)

Sorry for the latest shorty message ,but i was late.
So your implementation is similar to design applied in some ORM for example.
Those are using the activerecord & crud pattern:
http://en.wikipedia.org/wiki/Active_record_pattern
http://sumanthtechsavvy.blogspot.com/2008/04/activerecord-crud-operations-1.html

I think DAO is a pattern for do more complex requests and operations for a type entity.
For example: dao.getActiveMembers(), dao.deleteOldies()

But it is possible that your idea is “fit” to the DAO’s definition
and only i have another point of view in this topic :)

Cheers