Are there any issues with user variables ( SET @variable:=) overflowing
memory on the server?
I am considering using user variables to implement a simple psuedo stored
procedure API whereby an API user can set variables for a query in one
function, and call the query later on in another function. If I do this the
way I am planning, the variable names will be controlled outside of the API
and in theory a large number of unique names could build up. At any one
time I wouldn't need most of them, but I don't see any way of removing them
once set. Might this be an issue, or is there some garbage collection
and/or memory limit on the variables. Should I clear them after using them
by setting them to NULL?
Thanks,
eRic
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
