728 Commits

Author SHA1 Message Date
Etienne Trimaille
8f33d5ee70 Upgrade DBManager and Grass plugins to Python 3.X 2023-04-26 08:24:00 +10:00
Matthias Kuhn
f591542ffe
Merge pull request #50740 from DelazJ/txIssues 2022-12-17 08:37:12 +01:00
Harrissou Sant-anna
d6b5b070d8 Remove unicode string notifier from python files 2022-12-11 08:58:21 +01:00
Harrissou Sant-anna
9f127b2815 More string fixes and make a few more available for translation 2022-12-11 07:37:55 +01:00
Harrissou Sant-anna
6a4684b94d
Solve misc issues reported in Transifex 2022-10-30 09:20:33 +01:00
Andrea Giudiceandrea
f865b3f534 [db manager] Fix import layer encodings 2022-09-09 07:12:50 +10:00
Andrea Giudiceandrea
940d95c77a [db manager] Add tooltip to enconding settings 2022-09-09 07:12:50 +10:00
Nyall Dawson
c1dbc90d30 [db manager] Don't load preview layers into project
Fixes #47159
2022-06-16 13:54:55 +10:00
Sandro Santilli
51da2ef551 Trust primary key of layers setup by DBManager TopoViewer plugin
Removes two very expensive queries per TopoViewer instance
Closes #47389
2022-02-16 16:35:37 +01:00
nicogodet
ea981d89f9 Homogenize toMapLayer function definition 2021-11-08 10:13:28 +11:00
nicogodet
40df6ec76b Add geometryType() method to root Table class 2021-11-03 18:09:27 +01:00
Alessandro Pasotti
a329b88289 Fix DB manager trigger info dlg (less than)
Fix #45420
2021-10-19 05:37:20 +10:00
Augustin Trancart
061b810dac Fix behaviour of triggers when logging an existing layer
When adding logging via db manager to an existing layer, all the
time_start of existing features are still null. When we modify one
feature for the first time, the update trigger fires and insert a row
for the past state of the feature. In turn, this fires the INSERT
trigger for this row, and the execution goes inside the `if
NEW.time_start is NULL`, which set the end timestamp to NULL, making the
old row still visible in the _current view.

In other word, the insert trigger makes the assumption that a null start
timestamp means now, which is not true in the case described above.

This commit fixes this assumption by initially setting it to `-infinity`
for existing rows.
2021-10-06 12:00:39 +10:00
Alessandro Pasotti
5a572dacaa Fix DB manager postgis double query
Fixes #45318
2021-10-02 07:18:18 +10:00
Loïc Bartoletti
98ff01ea1c
Fix Z/M dimension URI via DB Manager. Fixes #34894 (#45223) 2021-09-28 21:14:45 +02:00
Alessandro Pasotti
387c403c2f First nail in the coffin of DB Manager
Replace DB Manager legend custom menu action with
C++ implementation for SQL layer
2021-07-22 10:18:13 +10:00
Andrea Giudiceandrea
828638f661
[DB Manager] Fix No Geometry tables
Avoid to add a nonexistent 'geometry' field to the fields list of No Geometry tables.
2021-04-23 08:25:14 +02:00
Andrea Giudiceandrea
2538612a21
[DB Manager] Fix recognition of project layers with Z/M…
…or CurvePolygon/MultyCurve/... geometry types as spatial layers.
2021-04-23 08:14:57 +02:00
Andrea Giudiceandrea
57f589dd36 [dbmanager] Fix deprecation warning
Replace deprecated QgsCodeEditor setMarginVisible() with setLineNumbersVisible() for SQL dialog windows
2021-03-29 08:18:39 +10:00
Julien Cabieces
1821d7af47 Run providers tests in different CI jobs 2021-03-23 10:53:38 +01:00
Marco Bernasocchi
60f788c91d
Allow loading GPKG layers with GEOMETRY type (#42253) 2021-03-16 15:58:55 +01:00
Nyall Dawson
1040fe8705 Don't silently swallow exceptions in python context managers
Notably this causes processing modules to silently fail to load
without any warnings if the required dependancies (such as pyscopg2)
are not installed
2021-03-04 07:39:47 +10:00
Morten Sickel
ead85b1004
Make the db managers import function more robust towards (some types of) invalid layers.
Fix #41152
2021-01-27 18:17:17 +10:00
Evan Derickson
d79100a204 List comprehension formatting 2021-01-24 16:34:35 -08:00
Evan Derickson
fe184e8e71 Formatting list comprehension 2021-01-24 16:34:03 -08:00
Evan Derickson
63e77371f6 List comprehensions to generators 2021-01-24 16:26:53 -08:00
Evan Derickson
8cd0f92139 Undo removal of else 2021-01-24 16:09:53 -08:00
Evan Derickson
beefb9ed45 Replace str format with str cast 2021-01-23 20:09:01 -08:00
Evan Derickson
4e41ee6db2 More list comprehensions, str.join() 2021-01-23 20:06:27 -08:00
Evan Derickson
4b50c1a7a7 For loops to list comprehension 2021-01-23 16:06:29 -08:00
Alessandro Pasotti
3a2b8f889a Optimize column information 2020-12-21 11:36:47 +01:00
Matthias Kuhn
bcbf71ea2f
Merge pull request #39947 from m-kuhn/db_mgr_error
[db manager] Show error messages directly in place
2020-11-29 20:33:43 +01:00
Matthias Kuhn
2a30091f2c Remove unused import 2020-11-25 20:44:16 +01:00
Matthias Kuhn
2b6eb652a4 Use Scintilla for word wrap 2020-11-25 20:42:30 +01:00
Alessandro Pasotti
6cbbf5ebd1 DB manager: PG read enum value for sslmode
Fixes #38245
2020-11-16 13:13:21 +10:00
Denis Rouzaud
eddf6feb45 modernize CMakeLists.txt files 2020-11-12 07:14:46 +10:00
Matthias Kuhn
0a0d27c980 [db manager] Show error messages directly in place
The old behavior was to open up a new modal dialog. Each time way to small to read anything
2020-11-10 23:02:37 +01:00
Nyall Dawson
8c623b268e Revert "DB manager: PG read enum value for sslmode"
This reverts commit 26e9ec98e76591286576d2dde098578877bef9c0.

It results in unfixable crashes on many platforms, likely due to some
issue in sip itself

Fixes #38393, reopens #38245

The original bug (being asked twice for credentials) is preferable
over a hard crash
2020-10-23 08:22:15 +10:00
Alessandro Pasotti
eb3c78d12d DB manager fix add comment while creating table
Fixes #38394
2020-09-25 10:56:13 +02:00
Alessandro Pasotti
3b6178ad3b
Merge pull request #38981 from elpaso/bugfix-gh38975-and-other-db-manager-issues
Bugfix gh38975 and other db manager issues
2020-09-24 18:42:56 +02:00
Alessandro Pasotti
871f534ef9 Fix PG db-manager rename schema
Fixes #38998
2020-09-24 14:23:26 +02:00
Alessandro Pasotti
9880a751a9 DB manager Fix SHOW in PG queries
Fixes #8975
2020-09-23 15:14:04 +02:00
Alessandro Pasotti
063b8daab3
Merge pull request #38940 from elpaso/bugfix-gh38092-executesql-feedback-followup
Be smart when adding limit: followup #8092
2020-09-22 11:32:27 +02:00
Alessandro Pasotti
ef02c54252 Be smart when adding limit: followup #8092 2020-09-22 09:26:13 +02:00
Juergen E. Fischer
a15fff158a Translation string fix 2020-09-22 09:12:15 +02:00
Alessandro Pasotti
6d866e3341 Address PR comments 2020-09-21 14:02:24 +02:00
Alessandro Pasotti
2dfc072fe7 Spellchecker, how picky you are 2020-09-19 11:30:55 +02:00
Alessandro Pasotti
d54c3101ae Add feedback to executeSql
Fixes #38092 by adding an optional QgsFeedback argument to
the executeSql method and by implementing the PQCancel
method in the PG provider internals.

While the cancellation works well for all supported provider while
fetching results in the loop, the cancellation of a running query is now
implemented for the postgres provider connection only because the GPKG
and GDAL both rely on GDALDatasetExecuteSQL which cannot be interrupted.

This PR also introduce a few optimizations in the PG DB-Manager
code that should probably fix also other "slowness" issues that
were reported after 3.x during PG query execution.

A small UX change in th SQL dialog makes it evident to the user that
a cancellation request has been sent to the backend: the button text
is changed to "Cancellation requested, please wait..." so that for
provider connections that are not able to interrupt the running query
and must wait for the fetching loop to exit from the exeuteSql call
the user knows that something is happening and that a cancellation
request has been successfully sent.
2020-09-19 11:15:41 +02:00
Matthias Kuhn
e4a767a39a Remove "Update options" button
It's hard to guess for a user what the button does.
And easy to achieve the same by changing the layer in the dropdown
2020-09-02 08:43:26 +10:00
Alessandro Pasotti
26e9ec98e7 DB manager: PG read enum value for sslmode
Fixes #38245
2020-08-13 12:48:02 +02:00