I've just tested in Master 9cae77f262,
It seems to works fine
many thanks for the explanation
Regards
Alessandro Pasotti-2 wrote
> On Tue, Oct 16, 2018 at 1:06 PM Antongeo76
> antoviscomi@
> wrote:
>
>> Alessandro Pasotti-2 wrote
>> > May be related to https://issues.qgis.org/issues/20094
On Tue, Oct 16, 2018 at 1:06 PM Antongeo76 wrote:
> Alessandro Pasotti-2 wrote
> > May be related to https://issues.qgis.org/issues/20094
> >
> > See also: https://github.com/qgis/QGIS/pull/8200
> >
> > On Tue, Oct 16, 2018 at 12:50 PM Antongeo76
>
> > antoviscomi@
>
> > wrote:
> >
> >> Hi,
>
nothing related with overflows as described in shown tikets... btw, please
give a check with master (not 2.18) nightly builds e.g. qgis-dev. Fix has
been merged and you can check if it works on on dev version not in 3.2.x.
Luigi Pirelli
Hi,
Any third party plugin enabled? There are some plugins that are/were
known/suspected to generate this overflow. You'll find related reports in
the bug tracker.
In 3.x, try to run on a clean user profile with no additional plugin.
DelazJ
Le mar. 16 oct. 2018 à 13:06, Antongeo76 a écrit :
>
Alessandro Pasotti-2 wrote
> May be related to https://issues.qgis.org/issues/20094
>
> See also: https://github.com/qgis/QGIS/pull/8200
>
> On Tue, Oct 16, 2018 at 12:50 PM Antongeo76
> antoviscomi@
> wrote:
>
>> Hi,
>>
>> This slowness is also present in QGIS 2.18 as well as in QGIS 3.2.3
May be related to https://issues.qgis.org/issues/20094
See also: https://github.com/qgis/QGIS/pull/8200
On Tue, Oct 16, 2018 at 12:50 PM Antongeo76 wrote:
> Hi,
>
> This slowness is also present in QGIS 2.18 as well as in QGIS 3.2.3
> and also occurs with fewer features in shapefiles
Hi,
This slowness is also present in QGIS 2.18 as well as in QGIS 3.2.3
and also occurs with fewer features in shapefiles (15000-16000 are enough),
slowness increases as the number of unsaved editing operations increases.
With the "attribute table" opened, even "merge elements" or "split
Hello,
I've found the refactor fields process to be a reliable and fast backup
option (plus being a process it now works in the background on a separate
thread and shows a progress meter so you've a good idea if it's actually
working!) if you're happy to have entirely new fields added.
I've had
My first suggestion would be for, after importing from csv, save it to
geopackages for the rest of the operations. Then, in the end export back to
the necessary file format. I think working directly on text files is not
optimal.
Best regards,
Alexandre Neto
A ter, 9/10/2018, 20:02, Rebecca
Hello,
A couple of colleagues and I have been wrestling with a similar issue to this
and I've been hunting around to see if it's documented, and happily saw this
email string. I've viewed the bug reports (both Kelley's and the related
#19771) and while they capture most of what we've been
Hi,
In SQL queries on databases like Postgresql it is common to use the Limit
operand to ask just a sample of the output to check if all looks OK without
reading the all table.
This situation made me wonder if this couldn't be a nice feature request to
the layers attribute table when working
tnx Kelly, this is your issue and it's ok:
https://issues.qgis.org/issues/20008
to everyone, please add any comment or info that can help to replicate/solve
Luigi Pirelli
**
* LinkedIn:
Hi,
Glad to hear that it helped to run the operations on a closed table.
Nevertheless, as Luigi said, it would make sense to submit an issue
report about this slowness.
The other thing one has to keep on mind:
The SQLite API is kind of limited. Only until recently, if you wanted to
rename
may you open an issue about this slowness with all details to reproduce?
Only with opened issue the project can allocate resources to fix them...
and we are just in bugfix period before the 3.4 release. So your
contribution would be precious.
tnx
Luigi Pirelli
Luigi, I'm pretty sure you just solved my problem. I tried a few operations
with the table closed and it was like night and day. That 400k field
calculator finished in mere moments! Thank you!!
On Wed, Oct 3, 2018 at 1:42 PM Luigi Pirelli wrote:
> can you test doing operations with field
can you test doing operations with field calculator without having the
attribute table opened? just a workaround could be to use a virtual layer
then save the entire layer later.
Luigi Pirelli
**
*
Hi,
I had similar problems with shp files in earlier version of QGIS. I would
reboot the Window machine and restart QGIS but the problem would start again
after a number of edits. I think it was a plugin that was causing a memory
leak. Try closing all the plugins and then re-starting Qgis.
17 matches
Mail list logo
