<div dir="ltr">An issue recently came up where someone was preparing a mighty large EXECUTE SCRIPT request, and bumped up against the limit that the statement parser statically determines that a script can have, at maximum, MAXSTATEMENTS statements, and sets the value of that to 1000.<div>
<br></div><div>I'm responsible for having set that value; would like to debate it a little bit.</div><div><br></div><div>The relevant data structure is that </div><div> int STMTS[MAXSTATEMENTS]</div><div>is used to indicate where the end of each statement is within the script being processed by EXECUTE SCRIPT.</div>
<div><br></div><div>I took the naive approach of declaring STMTS[] statically. Seeing as how we have had exactly one complaint about the matter since 2006, I rather think that this was an appropriate choice.</div><div><br>
</div><div>It would be some effort to switch to allocate dynamically; I wonder if it is apropos to:</div><div><br></div><div>a) Leave things alone, as there have been very few complaints over the last 7 years.</div><div><br>
</div><div>b) Increase the value from 1000 to something moderately larger, as people likely tend to have more RAM these days.</div><div><br></div><div>c) Go to the effort of dynamic allocation, so that arbitrarily large scripts are supportable.</div>
</div>