I don't know too much about posgresql (yet) however in Mysql you can send your queries which you think might return a large result set. a limit = 1,50 or something like that, which forces small result.

Other applications I have worked with have done other - not so elegant techniques, like counting the result set first, and displaying a warning to the user that the results would be over 500 records, and could take a while to download.

Personally, I would think that the UI, could if well thought of could handle it without prompting the user with -- this could take a while...but rather give them the first 100 or so records, with a flashing note saying press here for more records (something like looking up a google search)

just some thoughts.
Bob Lee


>Yes, the skill used in constructing a SQL has everything to do with speed. I've considered the possiblity that someone could use the VFP client I have made available to select all records from the testorders table. If there were 50,000 or 250,000 records, I assume my system would send all of them. This could slow my web/mail server down to a crawl. I think I will manage this by keeping the testorders table to a reasonable size, deleting records if need be, and run my performance test on another table. I spent this morning in the AdminphpPg administrator's app trying to work out a security scheme that make everything in the vfp2pg database available to the world at large while protecting everything else from harm.
>
>Time from Lunch. I'll check back later. Still have finished those returns from yesterday, but they have been electronically transmitted. Now I need to print/assemble the client's and my copies.