Has anyone else seen a case where passing defined constants to a GetSQL call confuses it so badly that it slows down by a couple of orders of magnitude? (0.02 seconds in SQL Developer, 1-2 seconds in the AppEng trace for the &sql_stud_pell.Execute() call)
Constant &c_emplid = "ZYXWVUT";
Constant &c_institution = "UMSXX";
Constant &c_aid_year = "1776";
<* &sql_stud_pell = GetSQL(SQL.UM_CL_STUD_PELL, &c_emplid, &c_institution, &c_aid_year); *>
&sql_stud_pell = GetSQL(SQL.UM_CL_STUD_PELL, "0000000", "UMS00", "2020");
Even more frustrating, if I run it as above, and then change it back to the commented out line, it still works! Until I let it sit over the weekend and re-run it Monday morning, at which point the slowdown reasserts itself.
All of the other GetSQL commands I'm defining in the same way, some with the exact same constants, act normally. I'll let it stand as it is, just so I have a working project, but I'd really like to know what mechanism I'm invoking, so I can try to avoid it going forward. (This was a recent rewrite - I was previously passing undefined local variables, hence blank strings.)
------------------------------
Garrett Fitzgerald
Senior Analyst Programmer I
University of Maine
------------------------------