24.05.2018 11:35, Dimitry Sibiryakov wrote:
24.05.2018 1:08, Vlad Khorsun via Firebird-devel wrote:
24.05.2018 0:39, Dimitry Sibiryakov wrote:
What visible changes can happen after upgrade of server version?
We have local server v4 and remote server v3. v4 runs external statements
against v3
and remote sessions have some context that is re-used by remote statements
somehow.
Then remote server is upgraded to v4 and remote sessions gets reset on re-use.
Now
remote statements can't re-use that context and behaviour could be changed.
From reading documentation I have a feeling that currently external connection is reused only within transaction. When local
transaction ends, connection is disconnected.
Yes, almost
Am I wrong?
Yes. Above i speak about v4 with connections pool, not about how it works
"currently".
4. Implement EXTERNAL DATA SOURCE database object and one of its property should
be flag to [not] reset external connection on re-use.
This is the best solution (as for me) but it might not fit into v4 release
schedule.
Release is not in sight yet and this object basically is one system table. I
think it will fit easily.
Not as easy. It also includes a set of DDL statements to manage this objects,
set of permissions, support in gbak, and, the most complex, good and as much as
possible complete desing.
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
