Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 11 to 12 of 12 total |
Convert DBISAM statement to ElevateDB |
Sat, Sep 5 2009 10:26 AM | Permanent Link |
"Malcolm" | Fernando Dias wrote:
> Malcolm, > > > After all the ng 'complaints' about the loss of 'EXISTS' for > > things like CREATE/DROP .. , I never even looked for WHERE EXISTS. > > They are completely different things: > You are talking about the DBISAM non-standard IF EXISTS and IF NOT > EXISTS clauses, used in DDL statements; this one is the standard > SQL predicate EXISTS, used to test if a subquery is empty or not. Yes, I realise .. now .. I just did not think! -- |
Sat, Sep 5 2009 11:03 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Fernando,
<< I have no idea if the tables involved are big or small, but in general, can this kind of statements execute faster if we select only one column, for example SELECT "Meet") instead of SELECT * in the sub-query? >> EDB will try to make it return a sensitive (live) result set, but if it can't then the number of columns selected matters. So, yes, it would usually be best to just specify one column unless you know for a fact that the sub-query can return a sensitive result set. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, May 7, 2024 at 02:40 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |