On 2020-04-29 19:34, Dmitry Yemanov wrote:
29.04.2020 18:50, Dmitry Yemanov wrote:
Client side cursor appears not too complex at the first glance, but
not sure do we want to have client or server side cursor.
Scrollable cursor is already materialized at the server side, so I
see no point
On 2020-04-29 18:50, Dmitry Yemanov wrote:
29.04.2020 17:50, Alex Peshkoff wrote:
Client side cursor appears not too complex at the first glance, but
not sure do we want to have client or server side cursor.
Scrollable cursor is already materialized at the server side, so I see
no point
29.04.2020 18:50, Dmitry Yemanov wrote:
Client side cursor appears not too complex at the first glance, but
not sure do we want to have client or server side cursor.
Scrollable cursor is already materialized at the server side, so I see
no point doubling efforts on the client. It should
29.04.2020 17:50, Alex Peshkoff wrote:
Client side cursor appears not too complex at the first glance, but not
sure do we want to have client or server side cursor.
Scrollable cursor is already materialized at the server side, so I see
no point doubling efforts on the client. It should
On 2020-04-29 08:19, Dmitry Yemanov wrote:
29.04.2020 00:36, Karol Bieniaszewski пишет:
May i ask if this is big developmenet cost to support it on the
client side api?
It's supported in the API, but not supported in the remote protocol.
IIRC, it can be easily implemented if a scrollable
29.04.2020 00:36, Karol Bieniaszewski пишет:
May i ask if this is big developmenet cost to support it on the client
side api?
It's supported in the API, but not supported in the remote protocol.
IIRC, it can be easily implemented if a scrollable cursor would disable
client-side asynchronous
May i ask if this is big developmenet cost to support it on the client side api?
Maybe it is shorter time than this disscussion
I try make this discussion lighter
Regards,
Karol Bieniaszewski
Firebird-Devel mailing list, web interface at
