• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

Design of the DB part

Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just started the SCJD assignment, and have some questions about the design of the database.
I was thinking of splitting up the data class into two parts; one for the "system" responsibilities, and one for the application spesific responsibilities.
The system part would include functionallity like adding records, deleting records, locking records and so on, while the other part would include the functionality the booking client needs like criteriaFind and bookSeats.
The latter interface will then be used in the rmi-part of the application.
There will be a base Data class which is subclassed by a BookingData class which implements the BookingDataInterface.
These are just some first thoughts about the design. Any comments will be appreciated
And one last question.. I was thinking of letting the Data class issue its own lock request when methods requiring record locking are called from the client. Or do anyone have a good reason why the client should call the lock request instead?
[ April 05, 2002: Message edited by: Geir Morten Hagen ]
I was her plaything! And so was this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic