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

URLyBird DB Design

 
Tim Fernandez
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Can anyone comment about this design:

DBMain interface
Data implements DBMain (all db logic are coded here).
DBConstants - All schema values are defined here(i.e., HEADERSIZE, MAGICCOOKIE, FIELDLENGTH, FIELDNAMES (Array), FIELDLENGTH (Array still)).

other parts like remote interface, adapter, etc are not yet coded so i've not included them here.

I'm concerned about the constants. Im not sure if this ok. I assumed that since everything schema related are specified in the ASsignment requirement then it's ok to define them as constants. Any comments?
 
Tom Henricksen
Author
Ranch Hand
Posts: 144
5
Eclipse IDE jQuery Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am not certain about this but would this maybe fit better in the suncertify.properties file? I know in my project B&S 2.2.3 I am supposed to have a suncertify.properties file. I planned on putting the Magic Cookie in there. I guess this is a Constants file vs. Property file question. I like property files since you don't have to recompile but that is a double-edged sword.
My 2 cents,
Tom
 
Tim Fernandez
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tom!

Thanks for the reply,

I dont think schema related info should be placed in the suncertify.properties. It just doesnt sound right. I just thought since its db specific then i guess, it's better kept inside the db package. And since the schema is not likely to change often, keeping it inside a constants file is ok. Schema related info are hardcoded in the assignment requirement so i guess keeping them constants is ok.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic