![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Mon, Nov 3 2008 3:04 AM | Permanent Link |
This UPDATE ran ok in DBISAM:
UPDATE MACLIENT C SET SIGLAVIACOD = S.CODIGO FROM MACLIENT C INNER JOIN MASIGLAV S ON C.SIGLAVIA = S.SIGLA WHERE C.SIGLAVIA IS NOT NULL; while in EDB needs to be changed to UPDATE MACLIENT C SET C.SIGLAVIACOD = (SELECT S.CODIGO FROM MASIGLAV S WHERE C.SIGLAVIA IS NOT NULL AND C.SIGLAVIA = S.SIGLA); The DBISAM to EDB changes say: "The FROM clause is no longer supported. ElevateDB can use correlated sub-queries in the UPDATE values and/or WHERE clause." Does mean "ElevateDB *can use* correlated" "must use"? or there are more ways to do it? and more efficient ones? Tiago Ameller tiago put_an-a-_in_a_circle sistemasc.net Sistema, S.C. | |
Mon, Nov 3 2008 12:23 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Tiago,
<< Does mean "ElevateDB *can use* correlated" "must use"? or there are more ways to do it? and more efficient ones? >> The text was essentially saying *why* the joins in the FROM clause, which are non-standard, are no longer necessary, i.e. EDB can use correlated sub-queries instead. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, July 15, 2024 at 07:03 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |