Details tab timing out

[jbrnz]

Another newbie here. I am working with a large database and am having trouble when I select the details tab before performing a search. If a search has not been performed the details tab tries to load every record in the table (for testing this is about 20,000 records) When I get the interface figured out it will be about 695,000 records. Once the details tab is selected I receive just the 20,000 of 20,000 records ahowing 1 of 20,000 but nothing else.

I have been searching the forums for a couple days and have not found what I am looking for.

My questions:

Is it possible to set the app up so that it does not display any results until a search is performed?

or if it is easier -

Can I hide the details and list tabs until a search has been performed?

Any help with this situation would be greatly appreciated.

Josh

[jbrnz]

I did find a solution to my problem on the forum. One way of solving the problem with browse details timing out, or if you want to remove the tab is to place the following code in apps actions.ini file with nothing else.

[browse]

By placing this in the actions.ini file it eliminated the browse tab, but made it so details can still be viewed in after clicking on them in the list.

Still getting a timeout when I select the list tab before performing a search and then attempt to view a record from that list. In case anyone else has same problem I will post the solution if I find it.

[shannah]

If a search has not been performed the details tab tries to load every record in the table (for testing this is about 20,000 records)

This sounds like a major problem, and should not be happening. The details tab should only load one record generally. If it is loading more than that we have a problem. Other than the "hanging" what have you observed that would suggest that it is trying to load the whole table?

Are you running a bare-bones app, or have you implemented any delegate classes?

-Steve

[jbrnz]

Thank you for the response. I am running the app pretty much bare bones. I have setup one delegate class so far, but now that I understand them a little better I will be creating them for each table. I don't at the moment know how to set this up through the delegate class, but you have a lot of good information on your board and I have already learned a boatload of concepts.

It seems that my system, if a large result set is found, returns an error if I try to view the details tab. Actually it just posts the the records number in the top left of the browser everything else is blank.

(Found 23130 of 29999 records in table song
Now Showing 2 of 23130)

I checked my apache log:
PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 131072 bytes) in /dataface/Dataface/DB.php on line 344

the code on that line is
$out[] = $row;

[shannah]

Try just raising the memory to 32 megs to see if that resolves it.

at the beginning of your index.php file you could add:

Code: Select all

ini_set('memory_limit', '32M');


[jbrnz]

Thanks Steve. That seems to have taken care of the problem. The app is now working smooth and is not returning the previous error.

Thank you very much for the support you provide to xataface users.