Please don't post to more than one forum. Cross-posting just makes following the threads of discussion so much harder.
The problem that you are talking about is not really MVC architecture at all and is really about database access design
patterns.
The patterns that you are applying are well-known and well-defined. In my opinion
you should create 2 separate classes:-
The first class would be a Value Object which is basically just a plain old
Java bean with the getters & setters.
The second class is a Data Access Object which instantiates the Value Objects by appling SQL SELECT statements against the database and handles the UPDATE, INSERT and DELETE statements.
Hope this helps
Andy Bowes<br />SCJP, SCWCD<br />I like deadlines, I love the whoosing noise they make as they go flying past - Douglas Adams