Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability to bulk load or update dataset to databases #24480

Open
qgib opened this issue May 19, 2017 · 3 comments
Open

Add the ability to bulk load or update dataset to databases #24480

qgib opened this issue May 19, 2017 · 3 comments
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request

Comments

@qgib
Copy link
Contributor

qgib commented May 19, 2017

Author Name: Regis Haubourg (@haubourg)
Original Redmine Issue: 16578

Redmine category:db_manager


Hi, currently, loading into postgres (or any other DB) just do individual INSERT commands.
This can be really slow.
Adding an option to load using COPY statements would speed up things a LOT. :)

see previous thread here :
[[http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-Postgis-loading-using-COPY-instead-of-INSERTS-td5320528.html#a5321038]]

@qgib
Copy link
Contributor Author

qgib commented May 19, 2017

Author Name: Giovanni Manghi (@gioman)


Or just use the Processing/ogr based tools to import data in postgis as they use COPY and are a whole lot faster than any other option in QGIS (and I created exactly for that reason).


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented May 19, 2017

Author Name: Regis Haubourg (@haubourg)


Yeah, and thank you for creating that algorithm. I tested it and it's nice. Anyway that sounds more like and alternative option in the UX. My opinion is that features exposed directly to users must be the most effective ones, and users should'nt have to dig into processing and know that ogr has a lot more options.
From a developer point of view, having a unique loader code, using OGR can be interesting to avoid code cluterring and efforts being duplicated.


  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented May 19, 2017

Author Name: Giovanni Manghi (@gioman)


Regis Haubourg wrote:

Yeah, and thank you for creating that algorithm. I tested it and it's nice. Anyway that sounds more like and alternative option in the UX. My opinion is that features exposed directly to users must be the most effective ones, and users should'nt have to dig into processing and know that ogr has a lot more options.
From a developer point of view, having a unique loader code, using OGR can be interesting to avoid code cluterring and efforts being duplicated.

I asked over and over to improve the situation of the DB manager loader, the d&d loader etc. has it didn't get any attention I had to implement what I needed... a blazing fast tool to load vectors in Postgis, in this sense I don't care if is duplicate of other tools are others don't care of users needs.

@qgib qgib added Feature Request DB Manager Relating to the DB Manager core plugin labels May 25, 2019
@nyalldawson nyalldawson added Data Provider Related to specific vector, raster or mesh data providers and removed DB Manager Relating to the DB Manager core plugin labels May 27, 2019
@alexbruy alexbruy added DB Manager Relating to the DB Manager core plugin Data Provider Related to specific vector, raster or mesh data providers and removed Data Provider Related to specific vector, raster or mesh data providers DB Manager Relating to the DB Manager core plugin labels Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request
Projects
None yet
Development

No branches or pull requests

3 participants