Seat references in the Segment

[Murat Balkan]

Hi all,
If we take the segment table in the db , it should also have the seat id column.
What I am thinking is,for each seat id for a segment, it will have a different row in segment table but I am not sure if it will be the best design.
Any comments?
Thanks,
Murat

[Murat Balkan]

any comments?

[Cleuton Sampaio]

Hi,

Depending on which persistency mechanism you are using... I have used DAO and including just the seatID column is enough.

[George Willy K]

Are you talking about DB design matching the Class structure?
In my opinion, segment repeating in the DB for each seat is not a good idea. In class design you can have a collection holding the seat reference and DB has a seperate table with seats and their segment Ids. This is what how I was thinking.

[Santiago Urrizola]

a better way to solve this problem is to model this in OBJECTS.
remember you are going to be evaluated in how you resolve and design the domain model in class diagrams (objects not tables) .... 44 points ....

[Dan Drillich]

I fully agree with Santiago!

As the big book (GoF) says:

... Object-oriented document editors typically use objects to represent embedded elements like tables and figures. However, they stop short of using an object for each character in the document, even though doing so would promote flexibility at the finest levels in the application.

BIG concept!

-- Dan

[Murat Balkan]

Thanks for your answers. I fully aggree with you.
But I am considering to use Entity beans which directly corresponds to tables. (Am I wrong?)
Ofcourse,my high level class diagram will not include those entities but I was wondering how will it look like in a detailed class diagram.
Thanks again,
Murat