![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
![]() |
Thu, Apr 5 2007 11:23 AM | Permanent Link |
"Harry de Boer" | LS
1.02 In EDBmngr in the SQL window you can set the "request sensitive result set". Is this the same as a 'LIVE' resultset? -If so, how can you still update records in the resiultset if you don't check that option -Why is a "select * from tbl where veld1 between 3 and 30000" faster with a LIVE resultset (I expected it to be the other way round) Maybe I am misinterpreting 'sensitive' ? Regards, Harry |
Thu, Apr 5 2007 12:48 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Harry,
<< In EDBmngr in the SQL window you can set the "request sensitive result set". Is this the same as a 'LIVE' resultset? >> Yes. << -If so, how can you still update records in the resiultset if you don't check that option >> Are you asking *why* you can still update rows if that option is not checked ? Or how to update an insensitive result set (static) so that the query result set rows are propogated back to the source table ? << -Why is a "select * from tbl where veld1 between 3 and 30000" faster with a LIVE resultset (I expected it to be the other way round) >> Sensitive (live) query result sets are simply the equivalent of opening a table and applying a filter, therefore they are very quick in most cases. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 5 2007 1:32 PM | Permanent Link |
"Harry de Boer" | >>Are you asking *why* you can still update rows if that option is not
checked >>? Or how to update an insensitive result set (static) so that the query >>result set rows are propogated back to the source table ? The *why* question. I expected not been able to update a record from a static resultset in EDBmngr (nice that that it can be done though). Harry "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht news:EB228BE5-D8F3-44D7-A647-6044C0E788BA@news.elevatesoft.com... > Harry, > > << In EDBmngr in the SQL window you can set the "request sensitive result > set". > > Is this the same as a 'LIVE' resultset? >> > > Yes. > > << -If so, how can you still update records in the resiultset if you don't > check that option >> > > Are you asking *why* you can still update rows if that option is not checked > ? Or how to update an insensitive result set (static) so that the query > result set rows are propogated back to the source table ? > > << -Why is a "select * from tbl where veld1 between 3 and 30000" faster with > a LIVE resultset (I expected it to be the other way round) >> > > Sensitive (live) query result sets are simply the equivalent of opening a > table and applying a filter, therefore they are very quick in most cases. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > |
Fri, Apr 6 2007 3:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Harry,
<< The *why* question. I expected not been able to update a record from a static resultset in EDBmngr (nice that that it can be done though). >> It's the same thing as with DBISAM. We allow it because it is useful in some cases where you want to use the static result set as a temporary table for further updating and processing. Although, it's probably less useful in EDB where you now have the CREATE TEMPORARY TABLE .. AS functionality. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, June 22, 2024 at 05:51 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |