Re: Can two sessions be bound in Oracle ?

ben brugman wrote:

>> 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
>
>

 From 50,000 feet up ... good design is a design that is robust and secure, the is alligned with relational
and/or object-based development standards and that does not force developers and DBAs to dream up
obscure solutions to what should be basic business processes. Everything you've written indicates that
you are trying to fix a design flaw and are looking for a source of electronic duct tape.

So my advice would be that you, and your co-workers, can spend the rest of your days working for
this employer trying to fix something that is rotten at its core ... or you can just put together a good
solid argument that will be understood by management ... which means cast it in man-hours and
dollars and have the thing fixed now. It won't fix itself and bad designers don't suddenly wake up on
some Monday morning and start designing better things.

You are correct that telling an application designer that they are incompetent is not a winning social
move and rarely makes employment more enjoyable. But there are other solutions. One is to throw
up your hands and say "I don't know how to solve this problem" and let them stew in their own
juices. Don't be so fast to cover up for the incompetence of others. I doubt they will rush to the rescue
to cover for yours.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)