Re: Need To Dummy-Down Oracle

To Jump Back In

I think I was the first to suggest disabling the constraints. I would be given 50 lashes with a wet noodle if as a DBA I was suggesting removing them. Sometimes constraints can prevent necessary maintenance, so it is not that unusual for a given process to be run while a db has no other users that disables the constraints, does its task, then re-enables them. This was what I was suggesting.

In article <366AD9D4.1261D8A8_at_teleport.com>,   mds_at_teleport.com wrote:
> No, I don't believe the datawindow would change itself. It could be that the
> column(s) you want to update were not specified as being updateable
> originally. It's hard to say for sure without seeing it, but I still think
> that the datawindow is the problem. I have occasionally run into situations
> similar to yours and it has always turned out the the update properties of the
> datawindow were not properly set.
>
> If I may, I would suggest that attempting to remove the RI constraints on your
> database is probably not the best way to approach the problem. The
constraints
> are there to serve a purpose, and if you succeed in removing them and then
> update the tables via some application, you will have put yourself in the
> position where the data could become corrupt.
>
> Doug Stone wrote:
>
> > >This is one of the most common datawindow problems. When you change a
> > >datawindow after it was originally created, PowerBuilder often requires
> > that you
> > >manually specify the new column update properties (I suspect that this is
> > for
> > >safety purposes).
> > >
> >
> > Michael, thanks for the feedback. Since we did not manually change the DW,
> > are you suggesting that the DW would change itself because of new RI being
> > specified?
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon Dec 07 1998 - 14:29:28 CST