Re: Q: LOV on the web. SLOOOOOW! Help me.

Hi Gary

This feature already existed in the eighties. Basically a LOV at that time resulted in a full table scan, and your post makes me think this didn't change. At that time we used two little tricks:
First, if there is a primary key on the table, just add a dummy where clause : 'where key > 0' or 'where key > chr(0)' This may not work with the cost based optimizer but it's worth a shot. In the past this resulted in the primary key to be used.
Secondly, it happened quite frequently there was a limiting condition derived from other columns in that form. Including those conditions in the where clause usually also brought some relieve.

Hth,

Sybrand Bakker, Oracle DBA

Gary Assa wrote:

> We are trying out running some Developer 2000 forms on the web, but the first
> time that an LOV is chosen, it takes an unbelievable long time for the LOV
> to appear. I mean really long. After the first one, all other LOV's are
> quick. I can understand a little delay, but is there any way to optimize them
> to appear quicker??
>
> I know I haven't given much info like what version, O/S, etc, but I thought
> maybe there were similar experiences and a little trick that people would
> have that is platform/version independent.
>
> --
> ------------------------------------
> If you have a condom and sunscreen SPF 15 or greater, than it's safe to look at
> http://www.panix.com/~gsa/index.html
Received on Fri Sep 11 1998 - 13:30:40 CDT