Does this sound like a good design for simple db lookup?

Question

I want to separate the gui form the behind the scenes stuff so 2 classes. One for the gui (gui.java) and one for the database stuff (dbQuery.java). I know the syntex is not accurate but it's sort of pseudo-code - Here's how it looks:
public class gui extends JFrame {
   string name, address, city, state, id
   public static void main {
      create gui         //all the swing stuff goes here
      actionlistener{          //waiting for button to be clicked
         when button is clicked,
         dbQuery dbq = new dbQuery(id)
         name.setText(dbq.getName())
         address.setText(dbq.getAddress())
         .....        //get the rest of the information needed
class dbQuery{
   dbQuery(string id){
      //do all the stuff to get connection. create statment, get sesult set...
      rs.next();
      string name = rs.egtString("Name");
      //.... assuming all db fields are appropriately named
}This is my first attempt at designing more than "Hello World" and your input truly is appreciated!
Merry Christmas!

Answer 1

I am partial to the database layer and the gui layer using a primitive and collections of primitives to share data.
A primitive is implemented as a class in java but it is not an object. Rather it just serves as a convient way to group the certain attributes together. Like this
     class CustomerPrimitive
          public String name;
          public String account;
          public Boolean preferedCustomer;
          public Double accountBalance;
.When I use primitives I tend to use objects rather than java primitivers (Integer rather than int.) This allows me to use the primitives for queries also - a null means don't query on that. In addition it allows me to return null values as nulls.
It is important that a primitive not have any substantial behaviour. For example there could be a validation method that verifies that the account number is not null. But there must not be a validation method to verify that the account number is unique. The first is implemented using simple java (perhaps with java.lang), while the second requires the interaction of numerous classes.