|
> -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / Paul Tuohy > Sent: Monday, July 26, 2004 6:58 PM > > But I think that a combined view/index would be the ideal solution. And it > should be possible since it is already there in DDS. > > An SQL index is a keyed logical. i.e. there is an access path entry for > every row. > An SQL view is a non-keyed logical. i.e. there is no access path. > > If you define a DDS logical with Sequence (a key) and select/omit logic, > then the access path only contains the rows that meet the selection > criteria. i.e. selection criteria is checked when the row is > inserted/updated. I want SQL to allow me do this! > If you specify DYNSLT, then the access path contains all rows and the > selection criteria is checked when the access path is read (which is what > SQL Select does using a view and an index). > > Clear as mud :-) > > Paul Doesn't it seem likely that someone somewhere wrote an article that compares SQL & DDS "logicals"? I looked briefly, but didn't find anything. Anybody have a useful reference? tia, db
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.