Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Help with SQL constraint
On Feb 16, 5:01 pm, DA Morgan <damor..._at_psoug.org> wrote:
> dean wrote:
> > On Feb 16, 11:32 am, DA Morgan <damor..._at_psoug.org> wrote:
> >> dean wrote:
> >>>> As I presume you intend to put this into production there is no more
> >>>> help available from me. YOYO. There is one and only one solution ...
> >>>> correctly model your business requirement.
> >>>> --
> >>>> Daniel A. Morgan
> >>>> University of Washington
> >>>> damor..._at_x.washington.edu
> >>>> (replace x with u to respond)
> >>>> Puget Sound Oracle Users Groupwww.psoug.org-Hidequoted text -
> >>>> - Show quoted text -
> >>> Hocus-pocus trick, no. Magic, maybe. It is unique data for one
> >>> particular value of the stated field.
> >> I disagree. I understand your intent but I disagree with trying to play
> >> games with relational integrity. Remodel it.
>> >> no doubt a poll of the vast majority here would similarly demonstrate
> >>>> There is one and only one solution ... correctly model your business requirement.
> >>> Why do you think that productions systems are always so easily
> >>> changed? How many companies have you consulted for that could just
> >>> clean-sweep their database design and not go out of business? I work
> >>> with a set of railroad companies that are still using 1960s
> >>> technologies on proprietory mainframe systems, maybe I should suggest
> >>> they upgrade some time!
> >> I've so far worked for small insignificant firms like AT&T, Boeing,
> >> Washington Mutual Bank, and the like. Somehow they've succeeded in
> >> working within a relational database without playing such games and I've
>> >> determined the solution absent the tool and now are trying to make the
> >> I may be totally off-base and if so I apologize. But it seems you have
>> >> (replace x with u to respond)
> >>> The table in question is at the heart of a large system. I'm running
> >>> some update queries on the table, and I think if I could join it
> >>> properly to another table I could get the update to run faster. It
> >>> would be an updatable join rather than an 'exists' query.
> >> I think you can't. Or at least not the way you are trying to do it.
> >> Reconsider alternative methods of accomplishing the goal.
> >> --
> >> Daniel A. Morgan
> >> University of Washington
> >> damor..._at_x.washington.edu
>> >> determined the solution absent the tool and now are trying to make the
> >> I may be totally off-base and if so I apologize. But it seems you have
>
>
>> > transaction, but was taking 40 minutes to run when placed at the end
> > The query in question is an update query
> > that was working in 10 seconds flat when outside of a long
>
>
>
>
>> > transaction. The execution plan was identical in both cases. Maybe
> > We were
> > not running out of rollback space, or memory, as far as we could tell
> > (there were no error messages), it was just slower when put in a long
>
The trace files are no longer available, and as I said I had them looked at already. But what I would find advantageous is a better technique for updating such joins as discussed, as there are several tables of similar construct that prevent an updatable join. Received on Sat Feb 17 2007 - 00:40:25 CST
![]() |
![]() |