I haven't heard anything since a week now after I have sent a small complete stand-alone script which shows that SapDB delivers wrong results to correct SQL queries. I cannot understand why SAP remains silent on this matter.
Because you so eagerly comment on little details and hick-ups of the database, how about evaluating this major bug in the database kernel which additionally is a real showstopper in a commercial project with a big German chemical corporation? Early next month, we will have to recommend the database to use which, if the bug remains open, must be Oracle. I do not like Oracle and would like to give SAP a chance, but please, act.
Still, we have other customers for our product and and would like to see the bug fixed.
mfG
Falk Langhammer
Becker, Holger schrieb:
> could you please send me a small example with table and index definition
> and some data because I want to reproduce the problem here with the
> development release and I'm not able to get the wrong results with my tests.
No problem to reproduce the bug. I have prepared a little example for
You (in the text-attachment).
-- Dr. Falk Langhammer Living Pages Research GmbH Kolosseumstr. 1a D-80469 Munich, Germany mailto:[EMAIL PROTECTED] http://www.living-pages.de Phone +49 (89) 189 207-27 Fax +49 (89) 189 207-29 Mobil +49 (171) 79 39 667 mailto:[EMAIL PROTECTED] (urgent SMS with subject header)
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
