Re: Two interesting features of Sybase that Informix may want

Peter Lancashire wrote: > > SET TRANSACTION is similar to noholdlock but not specific to a single > SELECT - it applies to an entire transaction. However, it is ANSI > standard. Does Sybase offer it? Yup, But the nice thing about this feature is that you can dictate the isolation level at the query level. This is important when you consider that you will need to know the current isolation level, store it, and then reset it after your query. By doing the isolation level at the query level, you don't need to do that. That's why its a nice feature. What's interesting is that 7.3 is supposed to allow one to specify the index that a query uses. Believe me, this is an excellent feature. Considering that the optimizer doesn't always work the way we want it and a complete sequential scan of a mere 1.5 million rows versus an index'd scan increases the process time by hours! :-( Since Informix and Sybase both offer this, (Does Oracle?), I'm going to forward a code segment to rogue wave recommending that they modify their RWDBSelector (??) class to include this as an option. I don't know who else is using roguewave, but they do have some nice class libraries. Cheers! -Mikey -- #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resembalence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** * Attention * -*- Due to AGIS's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until they modify their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************