20.05.2018 14:15, Mark Rotteveel wrote:
On 20-5-2018 13:00, Vlad Khorsun via Firebird-devel wrote:
I plan to introduce new database object "EXTERNAL DATA SOURCE" since initial
implementation of EXECUTE STATEMENT ON EXTERNAL, but I never have time\priority
to implement it, unfortunately.
The question at this topic is: should we add some way to clear session state
when
connection is known to be reused ? If yes - how it should be seen by a user (SQL
statement, API call, both ?)
I can think of use cases where clearing session state can be useful (eg connections in a application-side connection pool), and I
think exposing it as SQL should be OK, as that will give more flexibility in use. I would expect this to work with execute immediate
(but also using prepare/execute).
Ok, SQL statement, accounted
I would expect such a feature to reset all session state to the initial state
on connect, including things like
* Clear context USER_SESSION
* Reset role to the initial role specified on attach
* Reset other session configuration (eg DECFLOAT behavior, timeouts, session
timezone, etc)
Clear GTT's also.
Regards,
Vlad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
