[gdal-dev] ogrinfo UPDATE performance request

2022-06-08 Thread Andreas Oxenstierna
Dear developers Ogr SQL update capabilities are really impressing but there is one major performance issue with update of many features, exemplified by: ogrinfo -dialect sqlite -sql "UPDATE SET x = 1" PG:”" This is painfully slow because ogr updates features one by one and furthermore updates

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-08 Thread Alexandre Gacon
Hi, If you work with a Postgres database, why don't you do this directly in the database? It seems odd to use ogrinfo to do such updates in database. Regards Alexandre Le jeu. 9 juin 2022 à 08:50, Andreas Oxenstierna < andreas.oxenstie...@t-kartor.com> a écrit : > Dear developers > > Ogr SQL up

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Andreas Oxenstierna
Of course I normally do this directly in the database with pgAdmin or psql. In this process scenario it is preferable if the complete process (this is the final step of approx. 10 gdal/ogr processes) can be executed in batch by a client with no psql access. We have to use psql if there is no acc

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
Hi, Do not use "-dialect sqlite" if you play with PostgreSQL but let GDAL to use the native PG SQL dialect. -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta Andreas Oxenstierna Lähetetty: torstai 9. kesäkuuta 2022 9.50 Vastaanottaja: gdal-dev@lists.osgeo.org Aihe: [gdal-dev] ogri

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
is.it/gaia-sins/spatialite-sql-latest.html. -Jukka Rahkonen- Lähettäjä: gdal-dev Puolesta Andreas Oxenstierna Lähetetty: torstai 9. kesäkuuta 2022 9.50 Vastaanottaja: gdal-dev@lists.osgeo.org Aihe: [gdal-dev] ogrinfo UPDATE performance request Dear developers Ogr SQL update capabilities

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Jan Heckman
t GDAL to > use the native PG SQL dialect. > > > > -Jukka Rahkonen- > > > > *Lähettäjä:* gdal-dev *Puolesta *Andreas > Oxenstierna > *Lähetetty:* torstai 9. kesäkuuta 2022 9.50 > *Vastaanottaja:* gdal-dev@lists.osgeo.org > *Aihe:* [gdal-dev] ogrinfo UPDATE performance req

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
ialect for you? Have you tested the SQL with psql? -Jukka Rahkonen- Lähettäjä: Jan Heckman Lähetetty: torstai 9. kesäkuuta 2022 11.17 Vastaanottaja: Rahkonen Jukka Kopio: Andreas Oxenstierna ; gdal-dev@lists.osgeo.org Aihe: Re: [gdal-dev] ogrinfo UPDATE performance request Afaik as I know, sl

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Andreas Oxenstierna
ja: gdal-dev@lists.osgeo.org Aihe: [gdal-dev] ogrinfo UPDATE performance request Dear developers Ogr SQL update capabilities are really impressing but there is one major performance issue with update of many features, exemplified by: ogrinfo -dialect sqlite -sql "UPDATE SET x = 1" PG

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
etty: torstai 9. kesäkuuta 2022 9.50 Vastaanottaja: gdal-dev@lists.osgeo.org<mailto:gdal-dev@lists.osgeo.org> Aihe: [gdal-dev] ogrinfo UPDATE performance request Dear developers Ogr SQL update capabilities are really impressing but there is one major performance issue with update of many feature

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Andreas Oxenstierna
: Hi, Do not use “-dialect sqlite” if you play with PostgreSQL but let GDAL to use the native PG SQL dialect. -Jukka Rahkonen- Lähettäjä: gdal-dev mailto:gdal-dev-boun...@lists.osgeo.org>> Puolesta Andreas Oxenstierna Lähetetty: torstai 9. kesäkuuta 2022 9.50 Vastaanottaja: gdal-dev@li

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Jan Heckman
ault dialect once I edited the geometry column name to the one > I have in PostGIS. Are you sure that it requires SQLite dialect for you? > Have you tested the SQL with psql? > > > > -Jukka Rahkonen- > > > > *Lähettäjä:* Jan Heckman > *Lähetetty:* torstai 9. kesäkuuta 20

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Even Rouault
aanottaja:* gdal-dev@lists.osgeo.org *Aihe:* [gdal-dev] ogrinfo UPDATE performance request Dear developers Ogr SQL update capabilities are really impressing but there is one major performance issue with update of many features, exemplified by: ogrinfo -dialect sqlite -sql &qu

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
ilto:jukka.rahko...@maanmittauslaitos.fi>>, wrote: Hi, Do not use "-dialect sqlite" if you play with PostgreSQL but let GDAL to use the native PG SQL dialect. -Jukka Rahkonen- Lähettäjä: gdal-dev mailto:gdal-dev-boun...@lists.osgeo.org>> Puolesta Andreas Oxenstierna Lähetetty:

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
kesäkuuta 2022 13.02 Vastaanottaja: Rahkonen Jukka Kopio: Andreas Oxenstierna ; gdal-dev@lists.osgeo.org Aihe: Re: [gdal-dev] ogrinfo UPDATE performance request Hi Jukka, Not entirely sure what you mean by 'have you tested the sql with psql', since this is an ogr2ogr process which works. I

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Andreas Oxenstierna
, wrote: Hi, Do not use “-dialect sqlite” if you play with PostgreSQL but let GDAL to use the native PG SQL dialect. -Jukka Rahkonen- Lähettäjä: gdal-dev mailto:gdal-dev-boun...@lists.osgeo.org>> Puolesta Andreas Oxenstierna Lähetetty: torstai 9. kesäkuuta 2022 9.50 Vastaanottaja: gdal-

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Jan Heckman
C0%7C0%7C637903648638869695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PSddxQ5cOcxyh9rEAqWw791nqfWO%2B%2BKJbDSWGuSOOpY%3D&reserved=0> > > On 9 Jun 2022, 09:46 +0200, Rahkonen Jukka < > jukka.rahko...@maanm

Re: [gdal-dev] ogrinfo UPDATE performance request

2022-06-09 Thread Rahkonen Jukka
: Andreas Oxenstierna ; gdal-dev@lists.osgeo.org Aihe: Re: [gdal-dev] ogrinfo UPDATE performance request Hi Jukka, Thanks for all the dialect info. Reading your last message about testing the dialect in use, I have to admit that I did not think about native sql (dialect) being deduced from the