Hi,
the following works fine:
where CHAR(datecol, ISO) >= (select CHAR(datecol,ISO) from tab).
Many thanks!
Regards
Heidi
"Zabach,
Elke" To: "'[EMAIL PROTECTED]'" <[EMAIL
PROTECTED]>,
<elke.zabach@ [EMAIL PROTECTED]
sap.com> cc:
Subject: RE: insert statement fails
08.07.2003
09:12
>
> Hallo,
>
> I've got a problem with sapdb-version 7.4.3.25 on NT.
>
> From a tableT I made a copy T_clone (same structure, no data)
> in which I
> want to insert data from T which satisfy a certain search
> condition. The
> insert statement looks like
>
> Insert into T_clone select * from T where ....
>
> The result is always an error:
> ERR
> -24988,ERR_SQL: sql error
> 100,Row not found
>
> Executing only the select part of the whole statement gives a
> dataset of
> around 1500 rows.
> Any advice is welcome.
>
> Best regards
> Heidi Rufer
After some mails outside the list it was found out, that select ... where
datecol >= (select datecol from tab with exactly one row in) even when done
using SQLStudio/ODBC/JDBC works as expected,
returning some results BUT insert ... followed by the same select returns
row not found.
As we all know, those clients mentioned above use the date_and_time_format
ISO
--> the datecolumns in the upper select and the subquery have to be changed
from storing-layout to the format ISO.
For some reason the select does this correctly, the insert..select
'forgets' this for one side of the comparison --> ISO-format compares to
internal format, brrrh.
Workaround where CHAR(datecol, ISO) >= (select datecol from tab).
And the bug will be fixed within the next releases.
Sorry for any inconveniences.
Elke
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
