|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Interesting point. I've added referential constraints between two files. Even though the master file had a unique key on the PF I still got a message that it added a unique constraint. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Vernon Hamberg <vhamberg@attbi.com> Sent by: midrange-l-admin@midrange.com 04/24/2002 09:11 AM Please respond to midrange-l To: midrange-l@midrange.com cc: Fax to: Subject: Re: SQL help Just thinking - for once <g> In the old days we did not have unique constraints that could be attached to the physical, did not have even a primary key (which is unique). So this vulnerability existed all over the place. Even today, how many of us put all the unique indexes on a physical as a unique constraint? Isn't that what we'd need to do, in order to be completely safe from this vulmerabilty? At 10:04 AM 4/24/02 -0400, you wrote: >John, > >Couldn't agree with you more. I could never figure out why Sears so >heavily promoted NOT having your PF's keyed and depending on the LF's for >your keys...back in the old days...:) > >I always key them where I can....even if it's not unique. You never know >when you're going to need to use something like WRKDBF or DBU on a file >and need a nice, quick easy way to hit the desired records... > >Don in DC > >---- > >On Tue, 23 Apr 2002 jpcarr@tredegar.com wrote: > > > > > >Is this a bug? > > >Just one more reason why I like keys on my physical files. > > >Rob Berendt > > > > I couldn't agree more Rob. Just for the reason you showed. If your > > unique Key is on a LF instead of on the PHY, You will have exposure of > > dups. > > > > My UNIQUE's have always been on the PHY. > > (No I don't want to hear of Damaged Objects..... - After 15 years, never > > had one) > > > > John > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.