![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
![]() |
Wed, Mar 21 2007 12:50 PM | Permanent Link |
"Ole Willy Tuv" | create table t1 (col1 varchar(10));
create table t2 (col1 integer); insert into t1 values ('A'); insert into t2 values (1); insert into t2 values (2); update t1 set col1 = (select 'B' from t2 where col1 = 1); select * from t1 t1.col1 has been updated with null, instead of the correct value 'B'. Another problem I'm seeing is that EDB accepts a non-scalar subquery as source for a scalar assignment: update t1 set col1 = (select 'B', col1 from t2); The statement should raise an exception on the non-scalar subquery. The degree can be checked early (syntax check), while the cardinality must be checked after the result set has been processed. Ole Willy Tuv |
Wed, Mar 21 2007 4:35 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Ole,
<< create table t1 (col1 varchar(10)); create table t2 (col1 integer); insert into t1 values ('A'); insert into t2 values (1); insert into t2 values (2); update t1 set col1 = (select 'B' from t2 where col1 = 1); select * from t1 t1.col1 has been updated with null, instead of the correct value 'B'. >> Okay, I will check it out. << Another problem I'm seeing is that EDB accepts a non-scalar subquery as source for a scalar assignment: >> I relaxed the requirement - it uses the first row for now. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |