|Subject||Re: [Firebird-Architect] Re: External procedures: implementation|
"Jim Starkey" <jas@...> wrote:
>This requires a separate discussion. I wouldn't say I agree here.
> >As an example take a scrollable and updatable result set that is not
> >supported by Firebird. This type of result set is expected by the Sun
> >RowSet implementation. The RowSet API is used now in many different
> >components/applications. It was not possible to use them with Firebird
> >till JayBird 2.0 which emulates them by caching all the stuff in
> >memory. So, the same feature has to be emulated there too.
> I doubt that will ever be implemented inside the engine or server. It
> is a client side service that should be layered on the published
> database API. We may want to make it part of the client library, but it
> isn't a candidate for inclusion in the engine.