Re: Can two sessions be bound in Oracle ?

>
> This looks like bad design.
>
> Those things that are common to more than one module should be in module Z
and > > be installed
> with every installation.
>
> Perhaps kept empty until required ... but installed with every
installation none the less.

>>--
>>Daniel Morgan

Offcourse this has been realised within the team that there are some tables which should go in one of the modules and should be present at all times. (The basic module)
But other modules still have overlap and having one such (or several) basic modules does not solve the problem.

And I think a lot of what the architecs are doing IS bad design. But telling them that does not solve the problem. We still have to solve the problem that there will be more than one application module, which sometimes work together at a high level, work each on their datasets and the datasets are not totaly disconnected.

We could disconnect the datasets by cutting alle 'relations', and trusting totally in the business logic. I think that would be heading for dissaster, because on the first crash of the system and I think that the business logic will have crashed the data wil become logically corrupt. I prefer to keep all data which in one database with all relations and constraints as they should be. (Even if the access is modularised).

Question : What is good design ? What is bad design ? Although I know (sometimes) what is good and (sometimes) what is bad, I do not have a set of rules for this. Telling somebody his design is bad is therefore (sometimes) very difficult if you can not point out which rules he has broken.

ben brugman Received on Fri Oct 24 2003 - 10:38:23 CDT