Feature request #19614

Improved control over database tables in a processing model

Added by Magnus Nilsson about 2 years ago. Updated about 2 years ago.

Status:Open
Priority:Normal
Assignee:-
Category:Processing/Modeller
Pull Request or Patch supplied:No Resolution:
Easy fix?:No Copied to github as #:27441

Description

Hi
I would like to see improved control over what happens when writing to tables in databases (currently PostGIS and GeoPackage, but I guess this applies to SQL Server other databases as well, once write support for those is added). If the table already exists in the database, the user should be able to choose what QGIS will do when writing the model output:

  • Drop the existing table and create a new table with the same name
  • Overwrite/truncate the existing table
  • Keep the existing features in the table and add the new features to it

This should be configurable for each individual output table, in case the model writes to several output tables.

Anyone else interested in this?

History

#1 Updated by Alexander Bruy about 2 years ago

Magnus Nilsson wrote:

  • Overwrite/truncate the existing table

There is a "Truncate table" algorithm. Or it does not work for you?

Also available in: Atom PDF