Toad 15.1.113.1379
Problem:
On 15.0, it works, I have searched for value 2887
Raul
Toad 15.1.113.1379
Problem:
On 15.0, it works, I have searched for value 2887
Raul
Hi Raul,
We made an intentional change here. Incremental search causes all rows to be fetched. So it was possible to get an "out of memory" error here, if user started incremental search and there were too many rows to fit in memory.
The way it works now, is if the lookup pulls less than 500 rows, we know they are all in memory already and incremental search will work. If more rows remain after the initial fetch of 500 rows, then we don't know how many rows remain, so incremental search is disabled.
As a workaround:
Edit: I can make a change such that if you CTRL+END in the grid to intentionally cause it to fetch all rows, incremental search will be re-enabled.
-John
Hi
Ok, I agree this change was necessary.
Edit: I can make a change such that if you CTRL+END in the grid to intentionally cause it to fetch all rows, incremental search will be re-enabled.
This sounds good, it would be universal approach for other tables when user chooses so.
But, we are using this feature mainly for looking up classifier table records, we have 17k rows there and table size is only 2mb. I would presume, it would get quite annoying to scroll to the end each time.
I was wondering, can't you add some other criterias in addition to this 500 row limit. For example, when we have small table with no lob segments, then this incremental search is also enabled by default (in addition to that if table as less than 500 records).
Also, not sure what is defined as "small table", but I would guess table size less than 10mb indeed is small (but I'll let you figure that one out) and would fit to memory just fine.
Regards
Raul
Hi,
Yes, I think I can increase the row limit for this grid. Maybe checking num rows in dba_tables would be a good way to get table size.
-John
This view has data blocks column as well.
Table size can be retrieved using db_block_size.
Raul
Ok, next beta, incremental search will be enabled for tables with more than 500 rows unless they are "large". I do some math based on row size and num rows. I don't think it'll be disabled now for your 2Mb table.