[pgadmin-hackers] Server side cursor limitations for on demand loading of data in querytool [RM2137] [pgAdmin4] - Mailing list pgadmin-hackers

From Harshal Dhumal
Subject [pgadmin-hackers] Server side cursor limitations for on demand loading of data in querytool [RM2137] [pgAdmin4]
Date
Msg-id CAFiP3vxaM9ixpmaM04JAkTT1ONwmnMPwUCbK+kzCN+r6F+7-ZA@mail.gmail.com
Whole thread Raw
Responses [pgadmin-hackers] Re: Server side cursor limitations for on demand loading of data inquery tool [RM2137] [pgAdmin4]
List pgadmin-hackers
Hi Dave,

To implement feature #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

pgadmin-hackers by date:

Previous
From: Akshay Joshi
Date:
Subject: Re: [pgadmin-hackers] [pgAdmin4][PATCH] Table column edit breaks whenusing column level permissions
Next
From: Khushboo Vashi
Date:
Subject: [pgadmin-hackers] [pgAdmin4][Patch]: Fixed RM #2315 : Sorting by size is broken