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

[SIGéal via QGIS-Developer]

Great job !
It gave me the opportunity to discover some nice new functionalities 
added since QGIS 3.16.


Thanks,

--
Christophe Damour

Le 08/08/2022 à 12:52, Alexandre Neto via QGIS-Developer a écrit :

The link...


https://docs.google.com/spreadsheets/d/1VyC_kYJU3qmWrzXzjeZuHGBjwE6O2lPov_c0LnO-AUA/edit?usp=sharing

Alexandre Neto

A sábado, 6/08/2022, 21:08, Alexandre Neto  
escreveu:


Hi,

Sorry for the long waiting. I have made a functionality matrix for
db manager and possible alternatives. I am not sure if all is
correct so please feel free to edit or comment.

After your edits I will create the migragion feature requests.

Best regards,

Alexandre Neto

A segunda, 11/07/2022, 08:11, Alexandre Neto
 escreveu:

Hi Nyall,

A segunda, 11/07/2022, 00:47, Nyall Dawson
 escreveu:


I wonder if you'd be willing to lead an effort to document
the missing
functionality from dbmanager, and file QGIS tickets for
these and
assign them to a new project in the QGIS github for
"deprecating db
manager"? 



Sure I will! I am on vacations, but next week I will start
working on it.

Thanks!

Alexandre


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[SIGéal via QGIS-Developer]

Hello,

I fully support that -1

I submitted a feature request some weeks ago to suggest that Explorer 
SQL functionalities should work on a non modal way :

https://github.com/qgis/QGIS/issues/49091

--
Christophe Damour

Le 10/07/2022 à 03:02, Alexandre Neto via QGIS-Developer a écrit :

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 
 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@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[SIGéal via QGIS-Developer]

Hi,

+1 for improving QGIS UI consistency !

I recently posted a feature request about "Update SQL Layer" dialog 
which IMHO should be non modal : https://github.com/qgis/QGIS/issues/49091


Reading this discussion, I tested further browser functionnalities and 
came to the conclusion that "Execute SQL" dialog should also be non modal.


And I also wonder why these dialogs could not be included in the Browser 
non modal window, similarly to what is done in DB Manager.


Just my two cents...

--
Christophe Damour

Le 22/06/2022 à 02:43, Nyall Dawson via QGIS-Developer a écrit :

Hi list,

I wanted to raise the discussion around potentially demoting the DB 
Manager plugin to become an opt-in, not installed by default plugin 
available from the QGIS plugin repository only.


It's likely no surprise to anyone on this list, but there's been a 
multi-year effort (mostly thanks to Alessandro!) to move all the 
important functionality of db manager over to the QGIS browser. This 
was driven by a number of factors:


- It was confusing and messy to expose database management tools 
through two completely separate parts of the QGIS interface
- The DB Manager tools are written in provider-specific ways, and 
don't use generic QGIS database/provider API calls. As a result 
there's a lot of duplicate code there, and db manager doesn't gain the 
benefits of new data provider features. (E.g. only a subset of the 
databases supported by QGIS and the browser management tools are 
available for management in db manager)
- The DB Manager functionality wasn't available for other parts of 
QGIS/plugins/scripts/etc to reuse, whereas the browser functionality 
is all nicely exposed to PyQGIS and is used by other parts of QGIS, 
eg. processing tools.
- The Python code implementing db manager is fragile, and is subject 
to semi-frequent regressions/breakage (through no fault of the authors 
-- it's just the nature of complex python applications which aren't 
soaked in unit tests)


I'd say we've reached a stage where the browser now offers all the 
common functionality also available in db manager, and we can start to 
seriously discuss the future of the plugin.


My personal view is that we should demote the plugin to a 
community-maintained, non-officially supported plugin available only 
through the QGIS plugin repositories, and remove it from the default 
QGIS install.


Thoughts/discussion welcome :)

Nyall





___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] [Qgis-user] QGIS freezes for minutes when updated SpatiaLite SQL Layer

[SIGéal via QGIS-Developer]

I created an issue :
https://github.com/qgis/QGIS/issues/47906

I can reproduce it with a dead simple query : select * from table 
(returning ~ 800 rows).


And no problem with any query/database on QGIS 3.16.16 !

Thanks,

--
Christophe

Le 22/03/2022 à 10:41, Alexandre Neto a écrit :

It probably also has something to do with the query you are using.

Can you please create a ticket? Preferably with some sample data and 
project and explaining the steps to reproduce the problem.


Thanks

Alexandre Neto

A terça, 22/03/2022, 09:24, SIGéal via Qgis-user 
 escreveu:


Hi list,

QGIS 3.22/3.24 freezes with hourglass for about 2 minutes when I
click
on close button of Update SQL Layer dialog, even if I didn't
modify the
query.
If I click on Execute button, I get this error : "an error occurred
while opening GPKG dbname=..."
This happens with a big database file (600 Mb), only with with query
returning hundreds of rows.

I don't have any problem at all with old behaviour on QGIS 3.16.16
: DB
Manager opened when I click on Update SQL Layer.
So this sounds clearly like a regression linked to the new "Update
SQL
Layer" dialog/behaviour.

Thanks for any hint or work around,

-- 
Christophe Damour


___
Qgis-user mailing list
qgis-u...@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS freezes for minutes when updated SpatiaLite SQL Layer

[SIGéal via QGIS-Developer]

Hi list,

QGIS 3.22/3.24 freezes with hourglass for about 2 minutes when I click 
on close button of Update SQL Layer dialog, even if I didn't modify the 
query.
If I click on Execute button, I get this error : "an error occurred 
while opening GPKG dbname=..."
This happens with a big database file (600 Mb), only with with query 
returning hundreds of rows.


I don't have any problem at all with old behaviour on QGIS 3.16.16 : DB 
Manager opened when I click on Update SQL Layer.
So this sounds clearly like a regression linked to the new "Update SQL 
Layer" dialog/behaviour.


Thanks for any hint or work around,

--
Christophe Damour

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer