Armin Haaf wrote: > > 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) ?
It is neither possible for a customer to change the maximum internal row length, nor is it planned to implement it. Sorry Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
