Project

General

Profile

Bug #1121

Large plant queries cause Out of Memory error

Added by Gabriel Farrell over 16 years ago. Updated almost 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
misc
Target version:
Start date:
07/24/2003
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1121

Description

An unrefined plant query that results in the system tring to large numbers of
plant is both slow and memory hungry ( even resulting in the jvm consuming all
its memory resources ).

This could be solved in a number of ways:

1. Have a google type interface thus limiting the display to some limited number
of plants ( 10, 50, 100?).
2. Move away from the xml/xsl pathway, populating a jsp or creating html on the
fly from JDBC resultset ( or some simple java object like PlantsSummary).
3. Both.

History

#1 Updated by Michael Lee almost 16 years ago

not sure why this bug is mine.

#2 Updated by Gabriel Farrell over 15 years ago

This is less severe now that users cannot search using the dreaded empty
string ... which returns all plants. ( they could still do this with
plantname="%" query unfortunately but then they are being malicious ).

So we still need the pagination to really clear this up.

I suggest using the postgresql offset limit functions to achieve this.

#3 Updated by Michael Lee about 15 years ago

this is an old bug, now solved by the perPage style views

#4 Updated by Michael Lee almost 15 years ago

changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 1121

Also available in: Atom PDF