News from Dmitry Yemanov
Query cancelation
Implementation of the statement cancellation feature has been committed into the version 2.1. It works via the monitoring tables – you just need to issue the DELETE command against the MON$STATEMENTS table (there’s no API implementation yet). It could be done by the application itself (using a secondary attachment) or by a server administrator. Examples:
DELETE FROM MON$STATEMENTS
WHERE MON$STATEMENT_ID = ?
or
DELETE FROM MON$STATEMENTS
WHERE MON$ATTACHMENT_ID = ? AND MON$STATEMENT_STATE = 1 -- active
The feature works for both SS and CS engines. The client application receives the GDS error code isc_cancelled.
Trusted authentication on Windows
Ability to authenticate Firebird users through a Windows domain is now available in the source tree and will be included into the v2.1 release. An up-to-date client library is required in order to use this feature. CURRENT_USER represents a logged in Windows domain user in this case. It’s expected that firebird.conf will introduce an option allowing you to choose between native-only, trusted-only and mixed authentication modes.
Loading...
That’s great news!!!
But I have to ask a question.
Why do you consider so important “an API implementation” of what is available through SQL? I mean, each app that can connect to the server and issue a query, through whatever api, can take advantage of this and eventually a programmer can build a wrapper function around this query and use it much like a specific API function.
Running a query to cancel another one looks overcomplicated for the API user, so there’s a demand for the API implementation as well.
Thanks for the explaination!
Another question, are stored functions in the works?