LookUpDisplay and sort performance

Murat Yelkovan

unread,

Feb 14, 2008, 3:06:03 AM2/14/08

to

I have a datawindow that retrieves about 4000 rows. I am using this
datawindow for buffering treeview object. This datawindow has only an id
column with dropdown datawindow.I need to sort this datawindow with the text
of this id column, so I created a compute column with
LookUpDisplay(birim_id) for sorting datawindow.But It took more than 2
minuts for sorting datawindow on this compute column.Do you have any
sollution?Pb 10.5 build 7564Thanks..

Philip Salgannik

unread,

Feb 14, 2008, 9:30:29 AM2/14/08

to

If this is used as a datastructure for sourcing a treeview then why bother
with LookupDisplay, why don't you retrieve descriptions in a separate
column?

"Murat Yelkovan" <muraty...@yahoo.com> wrote in message
news:47b3f66b@forums-1-dub...

Murat Yelkovan

unread,

Feb 14, 2008, 9:43:52 AM2/14/08

to

Because the sql of the dropdown datawawindow is dynamic. Users set this sql
from your interface. I dont want to add this dynamic sql to the main
datawindow. Actually I don't aware of the low performance of the
lookupdisplay + sort. Why the performance is very bad?
"Philip Salgannik" <philema...@comcast.net> wrote in message
news:47b45085$1@forums-1-dub...

Philip Salgannik

unread,

Feb 14, 2008, 11:23:41 AM2/14/08

to

On a 4K rowset it is slow - it needs to evaluate (perform the lookup of the
display vale) for each row to perform the sort.
And I don't buy your argument about the dynamic nature of the dropdown
resultset, again for using the resultset of a dataobject retrieval to source
a treeview you picked a very expensive method for resolving descriptions of
your ids...

"Murat Yelkovan" <muraty...@yahoo.com> wrote in message

news:47b453a8@forums-1-dub...

Jeremy Lakeman

unread,

Feb 14, 2008, 5:20:53 PM2/14/08

to

Sort may evaluate the expression for every compare between rows that
is performed (I'm not certain of the implementation though).
Try creating a computed field with the lookupdisplay expression, and
sort on that.
If that doesn't help, add a dummy string column and copy all the
values from the compute to the dummy column like this:

dw_1.object.dummy.primary=dw_1.object.compute.primary

and sort on that.

No guarantee's that this will help though.

On Feb 15, 2:23 am, "Philip Salgannik" <PhilipSalgan...@work.com>
wrote:

> On a 4K rowset it is slow - it needs to evaluate (perform the lookup of the
> display vale) for each row to perform the sort.
> And I don't buy your argument about the dynamic nature of the dropdown
> resultset, again for using the resultset of a dataobject retrieval to source
> a treeview you picked a very expensive method for resolving descriptions of
> your ids...
>

> "Murat Yelkovan" <muratyelko...@yahoo.com> wrote in message

>
> news:47b453a8@forums-1-dub...
>
> > Because the sql of the dropdown datawawindow is dynamic. Users set this
> > sql from your interface. I dont want to add this dynamic sql to the main
> > datawindow. Actually I don't aware of the low performance of the
> > lookupdisplay + sort. Why the performance is very bad?

> > "Philip Salgannik" <philemaxNOS...@comcast.net> wrote in message

> >news:47b45085$1@forums-1-dub...
> >> If this is used as a datastructure for sourcing a treeview then why
> >> bother with LookupDisplay, why don't you retrieve descriptions in a
> >> separate column?
>

> >> "Murat Yelkovan" <muratyelko...@yahoo.com> wrote in message

Manuel Espinoza

unread,

Feb 14, 2008, 6:50:23 PM2/14/08

to

Sometimes it helps when you disable the repaint:

dw_x.SetRedraw(false)
dw_x.SetSort('my_column A')
dw_x.Sort()
dw_x.SetRedraw(true)

HTH

"Jeremy Lakeman" <jeremy....@gmail.com> escribió en el mensaje
news:5431888a-688c-425d...@t55g2000hsa.googlegroups.com...