Subject | Re: [Firebird-Architect] Re: External procedures: implementation proposal. |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2005-07-21T20:11:33Z |
Jim Starkey escreveu:
understood that the ResultSet is a "in-memory table".
Thanks.
Adriano
>>Isn't it a problem for procedures that return too many rows?I have not readed the specification document yet and was wrong
>>
>>
>>
>>
>It shouldn't be. The abstract class ResultSet specifies only the API,
>not the mechanism behind it. An Java implementation of external
>procedures would probably return an implementation of ResultSet that
>navigated the corresponding Java objects with JNI. In all likelihood,
>the Java ResultSet would itself be a Java wrapper around the C++
>InternalResultSet (also implementation of ResultSet). This would give
>the Java procedure code full access to internal engine SQL in the
>context of the client database attachment.
>
understood that the ResultSet is a "in-memory table".
Thanks.
Adriano