Archives of the TeradataForum
Message Posted: Tue, 19 Nov 2002 @ 15:08:34 GMT
Does anyone have suggestions as to the best approach to take when writing web pages that access Teradata? In particular, I am interested in techniques that return large volumes of data and the web application pages through the answerset.
It seems to me that it is common for the web application to re-execute the query just to advance to the next page of records. For example page 1 displays rows 1 to 10. When the user clicks on a next button, the query is re-executed and the cursor positioned to the 11 row and rows 11 to 20 are displayed.
This seems to me that it would create a strain on the box that the same query is executed multiple times. Perhaps it is not as bad as I think since only a small subset of rows are returned at any one time. (?) My impression would be that it would be better to execute the query once then navigate the recordset from within the application.
Any help, suggested resources etc...would be appreciated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|