[EMAIL PROTECTED] wrote:
A runtime context, usually simply called a context, is a handle to aAh. So then what you're talking about isn't even SQL as such, but a Pro/C++ feature that manages all this for you. (I don't remember anything like this in PL/SQL, anyway, and I haven't used Pro/C++).
an area in client memory which contains zero or more connections, zero
or more cursors, their inline options (such as MODE, HOLD_CURSOR,
RELEASE_CURSOR, SELECT_ERROR, and so on.) and other additional state
information.
For one thing, MySQL doesn't even have CURSOR for now (any cursors, anywhere), so you couldn't even fake this with MySQL.
Porting to MySQL may be quite a challenge for you. The first thing would be to try to wean yourself from the precompiler by coding explicit operations in native C (ODBC) or Java (JDBC). Then, isolate your use of CURSORs, etc., and try to emulate them in MySQL by fetching all the results and managing the "cursors" yourself in a compatibility layer.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
