but if the tables already contains dup records, how can u
make a unique constraint ? (even with enable novalidate)
--
From: Anshumn[SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 12:30 PM
To: Rahul
Subject: Re: Enforced Costraints ??
Hi Rahul
...
Regards
Rahul
--
From: Anshumn[SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 12:30 PM
To: Rahul
Subject:Re: Enforced Costraints ??
Hi Rahul,
That is true. In Oracle 8, there is option to enable the constraint in
novalidate mode or validate
DSS !
--
From: Robertson Lee - lerobe[SMTP:[EMAIL PROTECTED] ]
Reply To: [EMAIL PROTECTED]
Sent: Tuesday, June 12, 2001 4:00 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Enforced Costraints ??
am I missing something here ?? Why would you
-
Van: Rahul [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 12 juni 2001 11:56
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints ??
DSS !
--
From: Robertson Lee - lerobe[SMTP:[EMAIL PROTECTED] ]
Reply To: [EMAIL PROTECTED]
Sent: Tuesday
implement a PK with non-unique values.
Remco
-Oorspronkelijk bericht-
Van: Rahul [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 12 juni 2001 11:56
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints ??
DSS !
--
From: Robertson Lee
2001 14:31
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints ??
I disagree. A simple reason for a non-unique index to
enforce a primary key are is to allowing a temporary
state of non-uniqueness to be permitted during a
transaction. eg insert a batch of new records (some
-Oorspronkelijk bericht-
Van: Rahul [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 12 juni 2001 11:56
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints ??
DSS !
--
From: Robertson Lee - lerobe[SMTP:[EMAIL PROTECTED] ]
Reply To: [EMAIL PROTECTED
Title: RE: Enforced Costraints ??
Well, here's one problem - there is no guarantee that Social Security Number will indeed be unique. SS#'s are reassigned, just like phone numbers are.
IMHO, surrogate keys are always a good idea. Has anyone got an example of when a surrogate key
9:21 AM
To: Multiple recipients of list ORACLE-L
Subject:RE: Enforced Costraints ??
In a DSS environment, it is a standard practice to create
surrogate keys
for
primary key. I never had experience with this (having duplicates
in PK).
Perhaps a list member could tell what probs
: Anshumn[SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 12:30 PM
To: Rahul
Subject: Re: Enforced Costraints ??
Hi Rahul,
That is true. In Oracle 8, there is option to enable the constraint in
novalidate mode or validate mode. The novalidate mode is the enforce mode
will be enforced for the upcoming data only...
Regards
Rahul
--
From: Anshumn[SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 12:30 PM
To: Rahul
Subject:Re: Enforced Costraints ??
Hi Rahul,
That is true. In Oracle 8, there is option to enable
: Tuesday, June 12, 2001 10:31 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Enforced Costraints ??
Absolutely do not use ssn for a primary key. I ran into that as a
concern when I created a report. The ssn can be assummed by another
person, and you would have two persons
agree with Lee: you should never
implement a PK with non-unique values.
Remco
-Oorspronkelijk bericht-
Van: Rahul [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 12 juni 2001 11:56
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints ??
DSS
[EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 06:42:01 -0800
I have no real solid design experience, but in the current model that I am
working on I created this table...
AUDIT DENIED LOGONS
| ADL Userid |
| ADL DateTime
for the
primary key will be more balanced than if you used a sequence.
my $.02
Rachel
From: Grabowy, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 06:42:01 -0800
I have no real
SSN's are not recycled.
From the SSA OIG's testimony on SSN use and misuse before congress -
The SSN is a unique identifier
, Maheswara [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 9:21 AM
To: Multiple recipients of list ORACLE-L
Subject:RE: Enforced Costraints ??
In a DSS environment, it is a standard practice to create
surrogate keys
for
primary key. I never had experience with this (having
and therefore the index created for the
primary key will be more balanced than if you used a sequence.
my $.02
Rachel
From: Grabowy, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 06
random and therefore the index created for the
primary key will be more balanced than if you used a sequence.
my $.02
Rachel
From: Grabowy, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue
Costraints ??
DSS !
--
From: Robertson Lee - lerobe[SMTP:[EMAIL PROTECTED] ]
Reply To: [EMAIL PROTECTED]
Sent: Tuesday, June 12, 2001 4:00 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Enforced Costraints ??
am I missing something here
Yes, SSNs are NOT reassignable.
At 08:41 AM 6/12/01 -0800, you wrote:
SSN's are not recycled.
From the SSA OIG's testimony on SSN use and misuse before congress -
The SSN is a unique identifier
http://www.ssa.gov/oig/Testimony05222001.htm
SSN is a perfectly good PK for personnel
To: Multiple recipients of list ORACLE-L
Subject: RE: Enforced Costraints ??
Absolutely do not use ssn for a primary key. I ran into that as a
concern when I created a report. The ssn can be assummed by another
person, and you would have two persons with the same ssn. Plus the
already
.
-Original Message-
From: Rao, Maheswara [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 9:21 AM
To: Multiple recipients of list ORACLE-L
Subject:RE: Enforced Costraints ??
In a DSS environment, it is a standard practice to create
surrogate keys
Chris,
I was AGREEING with you! :) use login and datetime for the key.
Rachel
From: Grabowy, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 09:21:22 -0800
Ok, so I
created for the
primary key will be more balanced than if you used a sequence.
my $.02
Rachel
From: Grabowy, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 06:42:01 -0800
I
He sent them back. He also got a new SSN. This time from someone that was already
dead.
-Original Message-
From: Christopher Spence [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 12:16 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Enforced Costraints
PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 09:21:22 -0800
Ok, so I was over analyzing the PK on this table. (big grin)
I still don't see a need for a surrogate key for this table
]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 08:06:33 -0800
If user id is unique, not null, and never will be or will not change, then
no need for surrogate or datetime.
Surrogate keys are great because they are no hassle and easy. They do not
mutate 10 columns of a primary key
, Chris [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Enforced Costraints ??
Date: Tue, 12 Jun 2001 06:42:01 -0800
I have no real solid design experience, but in the current model that I am
working on I created this table
Interesting reference. Based on the contents of this reference, you should
not use SSN for a primary key unless you work for the IRS or a
state/county/city taxing authority. The SSA is arguing that use of SSN
should be restricted to taxing authorities and banned from use by other
government
On Tuesday 12 June 2001 09:41, [EMAIL PROTECTED] wrote:
SSN's are not recycled.
Wanna bet? Maybe not intentionally, but they certainly are.
What about the use of fabricated SSN's for migrant workers?
This is not the illegal use of false documents, but simply a
number made up by employers
SSN is a unique identifier for an ACTIVE Social Security Administration
account. They CAN be (and are) reassigned after the person is dead and all
their survivor's benefits have been settled up.
Also, if you are not an employer, you are heavily dependent on the person to
tell you what their
Ah, but you still don't necessarily know that you have the right SSN. I've
had two instances with SSNs, one working for a state's revenue department,
the other for an insurance company in payroll. I've seen tax returns with
many different people using the same SSN. (As I remember we had 13
On Tuesday 12 June 2001 03:26, Daemen, Remco wrote:
Not good enough ! According to various documents, you should add your own
primary key (surrogate key), which also makes it easier to keep track of
history and combine various sources. I agree with Lee: you should never
implement a PK with
To: Multiple recipients of list ORACLE-L
Subject:RE: Enforced Costraints ??
am I missing something here ?? Why would you ever need to be in that
situation (a table with non-unique values in a PK column) ?
Apologies if this is a no-brainer.
Lee
-Original
To: Multiple recipients of list ORACLE-L
Subject: Re: Enforced Costraints (sic) ??
Interesting reference. Based on the contents of this
reference, you should
not use SSN for a primary key unless you work for the IRS or a
state/county/city taxing authority. The SSA is arguing that use of SSN
Title: RE: Enforced Costraints (sic) ??
Gene you owed me more than that!
HA!
Kidding...
-Original Message-
From: Gene Sais [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 4:20 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Enforced Costraints (sic
At a previous govt employer, SSN's were the employee's id # until about 3 years ago,
when they converted all SSN employee id #'s to a sequence generated employee id. At
my current govt employer, SSN's are not used, employee's are assigned job # ids. Now
there is a reason for this. In the
of
history and combine various sources. I agree with Lee: you should never
implement a PK with non-unique values.
Remco
-Oorspronkelijk bericht-
Van: Rahul [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 12 juni 2001 11:56
Aan: Multiple recipients of list ORACLE-L
Onderwerp: RE: Enforced Costraints
Anshuman,
whenever u add a constraint to a table, oracle will make sure all the data
(if any)
confirms to the constraint added
you can enable or disable a constraint (even defer)... dont confuse urself
with the term enforcing a constraint.
Regards
Rahul
--
From:
40 matches
Mail list logo
