[QGIS-Developer] Time for db manager to become an "opt-in" plugin?

[Alexandre Neto]

Hello all,

-1 for me

I am big QGIS/PostGIS user and DB manager in QGIS allows me to do something
that you can't do elsewhere, run long spatial analysis using SQL.

I understand the development reasons for removing db manager from the
official release and I really enjoy all the effort that Alessandro put to
bring most functionality to the browser. Nevertheless, I don't think it
fully replaces db manager querying functionality, and I really don't think
it will ever do.

The execute SQL dialog is great and amazingly fast, but it doesn't replace
the db manager editor. The QGIS SQL Editor (db manager or not) needs to be
an independent window that one can keep open for as long as needed to
develop and run queries step by step, see the results, load them in the
project, re-run etc... Also, it is almost mandatory that the user, while
having the SQL script open, can check tables details, like column names,
preview their values, etc... to help write the queries. We need an
independent window or in the limit a panel to allow that together with the
browser panel.

This db manager functionality is unique, and is (in my opinion) one of the
reasons why QGIS is PostGIS de facto client.

There are other minor functionality that is still not present, but can be
added later, like being able to create and manage constraints. Or easily
create a view from a query.

I understand that for now the functionality I miss would be available as an
external plugin, but, not being in core, soon it will just stop working,
and no one will care. QGIS was born as PostGIS query and visualiser client,
in my humble opinion, by removing db manager at these stage we are
downgrading QGIS functionality.

Thanks,

Alexandre Neto





A sexta, 8/07/2022, 18:12, Paolo Cavallini via QGIS-Developer <
qgis-developer at lists.osgeo.org> escreveu:

> Hi all,
> are we going to implement this? Apparently nobody objects.
> I'd add to the list the Topology sub plugin by strk. Probably not widely
> used, but an unique feature.
> I confirm that in the meantime the table historicization has been
> broken, one more reason for not shipping DB Manager in the current state.
> Cheers.
>
> Il 22/06/22 07:55, Nyall Dawson ha scritto:
>
> > - Saving/re-running previously saved SQL queries
>
> very useful to me. also loading the result of a query as a new layer
>
> > - Switching to the simplified "SQL builder" dialog for creating a SQL
> query
> > - Truncating a table (this is available through a Processing
> > algorithm, just not via browser)
> > - Attribute index creation (this is available through a Processing
> > algorithm, just not via browser)
>
> handy but not crucial
>
> > - !! Support for editing an existing column (changing name/type). This
> > is the biggest functionality gap -- changing existing column types is
> > not available elsewhere in QGIS
> > - Listing database triggers
>
> I'd add storicization of a table - I couldn't find anything easier for
> this.
>
> Cheers.
> --
> Paolo Cavallini
> www.faunalia.eu - QGIS.org
> training, support, development on QGIS, PostGIS and more
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20220710/b793309e/attachment.htm>