Re: You have my sympathies

David, thanks.
(Of course the triggered sequence inserts are cached...which means whenever there's a rollback, well you seem like a smart guy so you get the picture.) There have actaully been other contracted developers (all of them working on this project are contractors--initially one guy bringing in help when he needs it) that have come in to help with the application that have expressed the exact same setiments that you have and within days they mysteriously got re-assigned by their company....YOUCH. It's a very bad relational design, and in all reality shouldn't be as hard as it has been. I think it's what happens when you have a developer designing Oracle Databases with no Oracle experience, used to designing small MS SQL Server stuff. (and most likely getting paid big bucks). Unfortunately as the DBA I haven't had much say in the design(alot of things done seem to be done secretely), unless things they give me just don't work....

DNP wrote:

> From David P.
>
> Feel free to copy my e-mail and show it to anyone you need to.
>
> Tell them it took me all of 5 mins to come up with my opinion; tell them
> 5 mins is all a decent developer would take to determine that the app
> needs rewritten.
>
> Obviously somebody's head is on the line as to the original
> implementation but the truth has to come out eventually.
>
> The only hard and fast rule in I.T. is that office politics and I.T.
> NEVER mix.
>
> regards,
>
> David P.
>
> Hello wrote:
> >
> > Referential Integrity constraints? heheheeh.....they don't exist. These
> > relationships between the tables aren't key defined....they are based upon trigger
> > inserted data based upon sequencing (concating the sequence number with varchar2
> > data).. The primary keys on the tables don't match between parent and child. :-))
> >
> >
Received on Thu Mar 09 2000 - 11:27:01 CST