Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Avoiding any locks in SQL Servers - read and understand....its magic.
Hello Niall,
See below:
> "VC" <boston103_at_hotmail.com> wrote in message
> news:jxwRb.163297$I06.1625632_at_attbi_s01...
> > Hello Galen,
> > "Galen Boyer" <galenboyer_at_hotpop.com> wrote in message
> > news:ud6955sg0.fsf_at_standardandpoors.com...
> > > On Mon, 26 Jan 2004, boston103_at_hotmail.com wrote:
> > >
> > > > Since Oracle does not have database constraints, one has to
> > > > code them manually as I did directly in the query.
> > >
> > > You basically lose all credibility when you make such
> > > statements. Why should anyone even try to make sense out of what
> > > you would want to show if you say such blatently incorrect things?
> > >
> >
> > Somehow I am not worried about my credibility. But, be a good chap,
> please
> > elaborate on such 'blatently' incorrect things, will you ?
> >
> > Thanks.
> >
> > VC
>
Ah, I see... I honestly could not figure out what he meant by "incorrect things" -- I just assumed that someone who tries to criticise so aggressivevly would have some familiarity with basic database concepts.
Anyway, traditionally the taxonomy is as follows:
o domain constraints -- not supported in 9i and below
o table constraints -- partially supported (unique/referential/check) in
9i and below.
o database constraints or assertions (SQL-92) -- not supported in 9i and
below.
A database constraint relates to either a set of rows of a table, or the
entire table, or a state required to exist among several tables.
VC
>
![]() |
![]() |