On 29 May 2017 at 20:21, Giovanni Manghi wrote:
> Hi Nyall!
>
>> Thanks for the confirmation. Just to clarify, this fix was part of the
>> sponsored bug fixing effort which is funded by the project from
>> donated funds. So the real thanks here belong to everyone who has
>> donated to QGIS in the
Hi Nyall!
> Thanks for the confirmation. Just to clarify, this fix was part of the
> sponsored bug fixing effort which is funded by the project from
> donated funds. So the real thanks here belong to everyone who has
> donated to QGIS in the past and made this possible!
sorry for asking again, i
On 29 May 2017 at 15:30, Ted wrote:
> Hi Giovanni
>
> Yes, confirm that it is working well now
> https://www.youtube.com/watch?v=qBh0pzI2A5c
>
> from over 2 min to 4 seconds to load the same table.
>
> BIG thanks for everyone behind the scene. I believe the fix is done by
> Nyall, so a spacial tha
Hi Giovanni
Yes, confirm that it is working well now
https://www.youtube.com/watch?v=qBh0pzI2A5c
from over 2 min to 4 seconds to load the same table.
BIG thanks for everyone behind the scene. I believe the fix is done by
Nyall, so a spacial thanks to him.
read over and understand that this issu
Hi, know issue,
already lengthly analyzed and already fixed, just wait for the next
builds (2.18.9).
cheers
-- G --
>
> Hi,
>
> I'm facing a HIGHLY DEGRADED performance with attribute table opening with
> version 2.18.x (2.18.8 and 2.18.7) when we have more than 100K rows. (in
> this case 1
Hi,
I'm facing a HIGHLY DEGRADED performance with attribute table opening with
version 2.18.x (2.18.8 and 2.18.7) when we have more than 100K rows. (in
this case 161K)
I'm looking at an OLD application done 5 years back with a custom QGIS 1.7,
PostgreSQL 9.0 and PostGIS.
The performance at that
