Persistence Connecting to Relational DB - Alternative 1

• Database access is not decoupled from application specific behavior

• Each persistent class performs the mapping and access to the underlying relations by itself

• Disadvantages:

  • high coupling between problem domain classes and DB structure
  • DB-specific code is intermingledwith different classes
  • poor portability of the application, since changes of the DB structure influence the application and vice versa

save()

: Calendarium

: Appointment

makePersistent

/* SQL-Code */

Previous slide

Next slide

Back to first slide

View graphic version