TPS Table with 357,899 records - times out

[rupertvz]

Hi Guys,

I have a TPS table with 357,899 records which I am trying to link / view in a NWB.
I have a simple filter to display some of the records.

I am getting:

This page isn?t working - didn?t send any data.
ERR_EMPTY_RESPONSE

With less records the table contents display correctly.

Am I perhaps doing something wrong?  Or is this amount of records too many for a TPS table to display?

[rupertvz]

When I remove the NWB filter, the NWB loads fine (showing all records)

When I replace the NWB filter, the more records matches the filter, the quicker the browse loads
With little or no records matching the filter, the browser times out.

[Robert Iliuta]

Hallo!

Can you post the filter?
Where you put filter code? in template or embed code?

Robert

[rupertvz]

Thank you Robert,

The filter works fine with less records
The problem seems related to the large data set.


I tried two different options in the template;

Option 1:
Kindly see screenshot attached, my filter value "Pfe" is stored in LOC:Pfe

Option 2:
'C007:Pfe = <39>'&p_Web.GetSessionValue('GLW:Pfe')&'<39>'

  * Where GLW:Pfe is my "Pfe" session value

[Robert Iliuta]

I do not use filter in template (very rare)
Try to use in embed code: Before Browse Loop > Set Filter

loc:FilterWas = UPPER(C007:Pfe)&' = <39>'&UPPER(p_web.GSV('GLW:Pfe'))&'<39>'
ThisView{prop:Filter} = loc:FilterWas

Check and see id you see any difference.
I have TPS with more then 800.000 records and show just fine.


Robert

[Bruce]

Hi Rupert,

a) Do you have a KEY on the C007:PFE field ?
b) Is the key set as Case Sensitive?
c) Is the field a string or a long?

cheers
Bruce

[rupertvz]

Hi Bruce,

a) Do you have a KEY on the C007:PFE field ?
I have a single key, with only one component on C007:Pfe (Not unique)
I also have other keys with C007:Pfe as a component

b) Is the key set as Case Sensitive?
No, this key is not case sensitive

c) Is the field a string or a long?
String(10)

[Bruce]

Hi Rupert,

The key exists, but is case insensitive. So the filter must be case insensitive as well. ie not

'C007:Pfe = <39>'&p_Web.GetSessionValue('GLW:Pfe')&'<39>'

but more like

'UPPER(C007:Pfe) = <39>' & UPPER(p_Web.GetSessionValue('GLW:Pfe')) & '<39>'

Cheers
Bruce