Обсуждение: Edit Data in Query Tool
Hello All,
How difficult would it be to include the edit data tool as part of the query tool's reporting panel? Ideally I would like to select from a table and then edit the results of that select directly; that would drastically improve my productivity.
On Sun, Jan 13, 2013 at 7:12 PM, Rishi Ramraj <thereisnocowlevel@gmail.com> wrote: > Hello All, > > How difficult would it be to include the edit data tool as part of the query > tool's reporting panel? Ideally I would like to select from a table and then > edit the results of that select directly; that would drastically improve my > productivity. Very difficult at the moment. We'd need a SQL parser in the client to help try to figure out if the result of a query is something that may be updatable. There is a patch to add a parsers in the works, but even with that, it would still be very far from trivial. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
I believe the way this sort of thing is done in tools like SQL navigator is, only select queries on individual tables with primary keys are updatable. I'm not sure if this condition is sufficient for updatability however. The tool may also need to reissue the query (or modify it) in order to get primary keys.
Is there a branch I could look at that contains the sql parser?
On Mon, Jan 14, 2013 at 6:01 AM, Dave Page <dpage@pgadmin.org> wrote:
Very difficult at the moment. We'd need a SQL parser in the client toOn Sun, Jan 13, 2013 at 7:12 PM, Rishi Ramraj
<thereisnocowlevel@gmail.com> wrote:
> Hello All,
>
> How difficult would it be to include the edit data tool as part of the query
> tool's reporting panel? Ideally I would like to select from a table and then
> edit the results of that select directly; that would drastically improve my
> productivity.
help try to figure out if the result of a query is something that may
be updatable. There is a patch to add a parsers in the works, but even
with that, it would still be very far from trivial.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Jan 14, 2013 at 6:02 PM, Rishi Ramraj <thereisnocowlevel@gmail.com> wrote: > I believe the way this sort of thing is done in tools like SQL navigator is, > only select queries on individual tables with primary keys are updatable. Yes, that's what we'd need to do - but it's not particularly straightforward. You'd need to parse the query client-side (bearing in mind it might be a 100KB script) to figure out if the results all come from a single table, then check if you've got all the primary key columns, and then figure out if any of the columns are aggregates or expressions, and finally enable editing if appropriate. Then... you'd need to have editing capabilities in the output grid of the query tool. That code is not exactly trivial either. > I'm not sure if this condition is sufficient for updatability however. The > tool may also need to reissue the query (or modify it) in order to get > primary keys. > > Is there a branch I could look at that contains the sql parser? No, it was posted as a patch to the mailing list a month or two back by Vladimir Kokovic. It should be easy to find in the archive (just make sure you look at the latest version). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company