Server side cursor limitations for on demand loading of data in query tool [RM2137] [pgAdmin4]

From: Harshal Dhumal <harshal(dot)dhumal(at)enterprisedb(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Server side cursor limitations for on demand loading of data in query tool [RM2137] [pgAdmin4]
Date: 2017-04-25 07:41:31
Message-ID: CAFiP3vxaM9ixpmaM04JAkTT1ONwmnMPwUCbK+kzCN+r6F+7-ZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Dave,

To implement feature #2137 <https://redmine.postgresql.org/issues/2137> we'll
need to use server cursor. However server cursor has some
limitation.
For eg.
1. It cannot execute BEGIN; query (basically user cannot start new database
transaction)
2. In case if Auto commit is true then we try to execute user queries
inside BEGIN and END when ever it's possible even though user has not put
BEGIN and END in his query.

Also not all queries executed using Query tool produces records as result.
So can we assume only
queries started with SELECT should be executed using server cursor to
support on demand loading.
Or should we give user an option to use on demand loading like we have
options for Auto commit? and Auto rollback?
In case of on demand loading option user will be responsible to execute
correct queries (queries which can be executed using server cursor)

Let me know your opinion on this.

--
*Harshal Dhumal*
*Software Engineer*

EnterpriseDB India: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Khushboo Vashi 2017-04-25 09:18:23 [pgAdmin4][Patch]: Fixed RM #2315 : Sorting by size is broken
Previous Message Akshay Joshi 2017-04-25 07:10:59 Re: [pgAdmin4][PATCH] Table column edit breaks when using column level permissions