jwdcfdeveloper
Programmer
Does anyone know how to prevent a cfquery tag from blowing up when a search returns more than 1000 rows of data?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
query that returns more than 1000 rows of data
- Thread starter jwdcfdeveloper
- Start date
- Status
What do you mean by "blow up"?
Are you sure you are not confusing the cfquery tag blowing up with the <cfoutput query=> tag? Assuming your server has sufficient ram/power etc and your sql is kosher, your cfquery tag shouldn't "blow up". On the other hand, outputing a large record set to a client could have the appearance of something blowing up.
In the case of outputing a large amount of records, you will want to implement multiple pages to view the results.
Are you sure you are not confusing the cfquery tag blowing up with the <cfoutput query=> tag? Assuming your server has sufficient ram/power etc and your sql is kosher, your cfquery tag shouldn't "blow up". On the other hand, outputing a large record set to a client could have the appearance of something blowing up.
In the case of outputing a large amount of records, you will want to implement multiple pages to view the results.
- Thread starter
- #3
jwdcfdeveloper
Programmer
No I mean that if I submit a query:
<cfquery name="getStuff" datasource="someDB">
Select * From aTable Where condition = "is met"
</cfquery>
And the query returns more than 1000 Records (i.e. getStuff.RecordCount GTE 1000), what can you do to prevent an error page from popping up? Is there anything you can do w/ caching, or some other work around that will prevent the query from functioning?
<cfquery name="getStuff" datasource="someDB">
Select * From aTable Where condition = "is met"
</cfquery>
And the query returns more than 1000 Records (i.e. getStuff.RecordCount GTE 1000), what can you do to prevent an error page from popping up? Is there anything you can do w/ caching, or some other work around that will prevent the query from functioning?
make sure you add indexes to your tablefields where possible. Before you run the whole query, you might run a smaller query like:
<cfquery name="qGetNumber">
select count(your_primary_key_field) as NumberOfRecords from your_table
where condition = "is met"
</cfquery>
<cfif qGetNumber.NumberOfRecords LTE 1000>
... run the original query
<cfelse>
...errormessage
</cfif>
I'm not sure if it will make a big difference though.
chau
<cfquery name="qGetNumber">
select count(your_primary_key_field) as NumberOfRecords from your_table
where condition = "is met"
</cfquery>
<cfif qGetNumber.NumberOfRecords LTE 1000>
... run the original query
<cfelse>
...errormessage
</cfif>
I'm not sure if it will make a big difference though.
chau
- Status
