Project

General

Profile

Bug #3625

DISCONNECT terminates the remote database connection to early

Added by Constantin Asofiei almost 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Constantin Asofiei almost 6 years ago

See the test in #3624-2 and #3624-3 - DISCONNECT is supposed to be performed only when all active procedures that reference the database end or stop.. This requires investigation to determine the behaviour at least for:
  1. DISCONNECT from a persistent program
  2. DISCONNECT from different stack depths (immediately after CONNECT, no program uses the target DB buffers between CONNECT and DISCONNECT, a program uses buffers, etc)
  3. DISCONNECT program ends with a STOP/ERROR/etc
  4. DISCONNECT is called, program ends and there is still DB usage on the stack, but further on another program is started which uses the DB - can this program use it?

Also available in: Atom PDF