From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | pgAdmin 4 commit: Use the same cursor object of a connection object onl |
Date: | 2016-05-12 07:53:36 |
Message-ID: | E1b0lRA-0005wh-GO@gothos.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Use the same cursor object of a connection object only from the same
server.
Current implementation keeps the cursor object in the 'g' (current
request context) object identified by the connection-id.
But - it fails to identify a different connection object request, when
we have same database name in different database server, it does not
able to identify it as separate request, Hence - now we will use
server-id qualified identifier for the same object.
Thanks Neel Patel for pointing out the issue.
Branch
------
master
Details
-------
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=7f790a7f4965bb0f0908127be2f554b5a4323a60
Modified Files
--------------
web/pgadmin/utils/driver/psycopg2/__init__.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2016-05-12 07:53:51 | Re: PATCH: Fixed sql execution issue (pgAdmin4) |
Previous Message | Murtuza Zabuawala | 2016-05-12 07:48:17 | PATCH: Fixed sql execution issue (pgAdmin4) |