Becker, Holger wrote: >> .... > > Unfortunately you are right, sapdb creates such a provisional result to > handle > the "or" qualification. > This is valid for every type of join not only self joins. > May be I'm wrong but I think your example will work without join. > For example > > select id > from foo > where (pos = 1 and txt = 'foo') > or (pos = 2 and txt = 'bar') > or (pos = 3 and txt = 'baz') > or (pos = 4 and txt = 'biz') > ); > > should give the result.
That's right, it's just a simplified example of our requirements to show the problem. Is it planned to optimize the way of joining in the sapdb development, or is it possible to increase the maximum internal row length (8088 Bytes) ? Armin -- Armin Haaf, mercatis information systems GmbH Marlene-Dietrich-Str. 5 Fon +49 (0) 731 98588 - 615 ___o 89231 Neu-Ulm, Germany Fax +49 (0) 731 98588 - 511 _\ <_ http://www.mercatis.de mailto:[EMAIL PROTECTED] (_)�(_) _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
