Book a Demo

Author Topic: How to model database views?  (Read 2404 times)

David ODriscoll

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
How to model database views?
« on: February 19, 2005, 02:48:41 am »
While I understand that EA is not a data modelling tool as such, I am very effectively using it as such.

However I am now considering adding some views to the data model, and am not sure how (or indeed if) this can be done.  There is no stereotype for views.

Does anybody have any suggestions?
« Last Edit: February 19, 2005, 02:49:44 am by DavidOD »
Regards
David O'Driscoll
Brisbane, Australia

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: How to model database views?
« Reply #1 on: February 22, 2005, 07:27:33 am »
I asked the same question back around the middle of January.  I was told that views are not yet supported, but the feature is comming soon.  Until then, I'm using the following technique:

I've added the sterotype <<view>> to the base 'class'. Then I add the view and underlying tables to the model using the 'Table' element on the structure menu.

I use the <<view>> sterotype on the table representing the view.

I use 'dependancy' links from the 'view table' back to the tables that support the view.

A 'realize' link back to the use case for a role actor completes the picture.

It doen't get the code generated for a view, but it effectively communicates my design to my programmers.
« Last Edit: February 22, 2005, 10:26:30 am by jeshaw2 »
Verbal Use Cases aren't worth the paper they are written upon.