Large plant queries cause Out of Memory error
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).
Updated by Gabriel Farrell over 19 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.