Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

NX: URLyBird return object

 
Rob Pearson
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm trying to nail down my interfaces between db/network/gui and trying to decide how to return results from the db to the gui.
I started with a Room object which knew about the room details (name,date,rate etc) with suitable get/set methods. Having read various posts about making things expandable/generic I decided this may be too specific so moved back to the String array as specified in the assignment interface. This will need some sort of meta-data (or hard coding!) to work out what values are in which position. I'm now looking at a cut-down version of a ResultSet, that implements just a few of the methods in the ResultSet interface, including a (cut-down) ResultSetMetaData.
This would require less changes if the database were to be replaced to a "real" database with, maybe a JDBC driver. Also ResultSets should be familiar to junior programmers, but I'm wondering if it may be too much effort.
What do others think?
I guess this doesn't help with what gets passed from the gui to the db? SQL is definatelty too OTT.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic