Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 2 of 2 total |
RI benefits? |
Tue, Feb 17 2009 11:35 AM | Permanent Link |
"James Relyea" | Referential Integrity doesn't cascade. Key integrity is kept intact by
default. From the help file of 2.02: "No Action" This is the same as Restrict "Cascade" Not supported currently "Set Null" Not supported currently "Set Default" Not supported currently "Restrict" If a primary key or unique constraint column is updated, then the update will be rejected if it violates any foreign key constraints Are there any benefits to using RI? --my benefit was typically letting the engine take care of my cascaded deletes 'cuz I'm lazy at times jr |
Tue, Feb 17 2009 1:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | James,
<< Are there any benefits to using RI? --my benefit was typically letting the engine take care of my cascaded deletes 'cuz I'm lazy at times >> Sure there are. RI at its very core has always been about *preventing* damage to the declarative relationships between base tables in a database. The cascade option was added as a plus to save some time, but it isn't anything that you can't do manually in a transaction anyways. If you plan on allowing outside update access to your database, then RI is a must to prevent logical corruption of the data through orphaned rows. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 5, 2024 at 10:18 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |