Re: [QGIS-Developer] Bug #21460?

> The best option is always come and collaborate with core team, in the way that is most practical to you. Well, that's why I came here because there's been no activity on that bug for a month except my own comments. No requests for more information like "please do X and tell me the output". I

Re: [QGIS-Developer] Bug #21460?

Thanks for that information. I was unaware there really is such a small community of developers. I guess that Gis software is specialised enough that there is not general interest to attract the wider community support that some of the major open source projects produce, whether this is a

Re: [QGIS-Developer] Bug #21460?

On Tue, Apr 9, 2019 at 7:00 PM Jonathan Moules wrote: > Hi Andrea, > > As always, I agree with you, but one thing: > > > After all, the GPL license is really clear on the matter: "THE ENTIRE > RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD > THE PROGRAM PROVE

Re: [QGIS-Developer] Bug #21460?

Hi Richard, On Tue, 09. Apr 2019 at 10:25:49 +0200, Richard Duivenvoorde wrote: > predecessors uuid[] DEFAULT ARRAY[]::uuid[], > And the "uuid[]" is not a very common type in the gis world. > > If I'm correct '{""}' (what QGIS now uses for NULL values if the column > has an array type) is a

Re: [QGIS-Developer] Bug #21460?

On Tue, Apr 9, 2019 at 11:16 AM Matthias Kuhn wrote: > Hi > > > I wonder, what is the best way to answer a question like > > > I was wondering when issue x is getting some attention? > > Assuming > - that "issue x" is very important for a user who asks the question > - that "issue x" is one of

[QGIS-Developer] Bug #21460?

Hi I wonder, what is the best way to answer a question like > I was wondering when issue x is getting some attention? Assuming  - that "issue x" is very important for a user who asks the question  - that "issue x" is one of 3000 open issues for a developer The best for the user would

Re: [QGIS-Developer] Bug #21460?

Agreed, thanks Richard for the link, and Nyall for writing the article. Il 9 aprile 2019 10:25:49 CEST, Richard Duivenvoorde ha scritto: >On 09/04/2019 03.41, Nyall Dawson wrote: > >> If you can suggest any ways to improve the wording of that post >(while >> keep the core message intact),

Re: [QGIS-Developer] Bug #21460?

Hi, Le mar. 9 avr. 2019 à 10:25, Richard Duivenvoorde a écrit : > On 09/04/2019 03.41, Nyall Dawson wrote: > > > If you can suggest any ways to improve the wording of that post (while > > keep the core message intact), please let me know. > > On Mon, Apr 8, 2019 at 4:30 AM Paolo Cavallini

Re: [QGIS-Developer] Bug #21460?

On 09/04/2019 03.41, Nyall Dawson wrote: > If you can suggest any ways to improve the wording of that post (while > keep the core message intact), please let me know. On Mon, Apr 8, 2019 at 4:30 AM Paolo Cavallini wrote: > > may I suggest you an interesting read? >

Re: [QGIS-Developer] Bug #21460?

Hi all, On 09/04/19 01:19, Nyall Dawson wrote: > On Tue, 9 Apr 2019 at 09:03, Cory Albrecht wrote: >> >> Hi Paolo, >> >> Might I suggest that you consider that not everybody has time to go an learn >> the codebase of QGIS to be able to know where to start for making changes >> themselves, even

Re: [QGIS-Developer] Bug #21460?

Hi, we have bug-fix period before each release which is funded by QGIS.org from donations. So usually bugs that are critical/regression/crash/corrupt data are fixed during that period for LTR and PR. Cheers, Peter On Tue, Apr 9, 2019 at 3:41 AM Nyall Dawson wrote: > On Tue, 9 Apr 2019 at

Re: [QGIS-Developer] Bug #21460?

On Tue, 9 Apr 2019 at 10:52, Cory Albrecht wrote: > > Hello Nyall, > > Oh, I am well familiar with the vicissitudes of getting work done in open > source projects - It's why I have donated to many opensource projects over > the decades that I have been using them, including QGIS. But just

Re: [QGIS-Developer] Bug #21460?

Hello Nyall, Oh, I am well familiar with the vicissitudes of getting work done in open source projects - It's why I have donated to many opensource projects over the decades that I have been using them, including QGIS. But just telling people "go fix it yourself" is not helpful. To be frank, it

Re: [QGIS-Developer] Bug #21460?

On Tue, 9 Apr 2019 at 09:03, Cory Albrecht wrote: > > Hi Paolo, > > Might I suggest that you consider that not everybody has time to go an learn > the codebase of QGIS to be able to know where to start for making changes > themselves, even if they happen to know C++? Especially if they have to

Re: [QGIS-Developer] Bug #21460?

Hi Paolo, Might I suggest that you consider that not everybody has time to go an learn the codebase of QGIS to be able to know where to start for making changes themselves, even if they happen to know C++? Especially if they have to learn the Qt framework at the same time. That consideration

Re: [QGIS-Developer] Bug #21460? | is QGIS non-commercial?

On Mon, 8 Apr 2019 at 19:22, Benjamin Ducke wrote: > > Hi Paolo, > > On 08/04/2019 10:30, Paolo Cavallini wrote: > > Hi Cory, > > > > On 08/04/19 00:57, Cory Albrecht wrote: > >> I was wondering when Bug #21460 > >> was going to get some attention? > >> It's

Re: [QGIS-Developer] Bug #21460? | is QGIS non-commercial?

Hi Paolo, On 08/04/2019 10:30, Paolo Cavallini wrote: > Hi Cory, > > On 08/04/19 00:57, Cory Albrecht wrote: >> I was wondering when Bug #21460 >>  was going to get some attention? >> It's about  QGIS not forming proper PostGIS SQL updates correctly, >>

Re: [QGIS-Developer] Bug #21460?

Hi Cory, On 08/04/19 00:57, Cory Albrecht wrote: > I was wondering when Bug #21460 >  was going to get some attention? > It's about  QGIS not forming proper PostGIS SQL updates correctly, > specifically for null values. may I suggest you an interesting read?

[QGIS-Developer] Bug #21460?

I was wondering when Bug #21460 was going to get some attention? It's about QGIS not forming proper PostGIS SQL updates correctly, specifically for null values. Thanks in advance. ___ QGIS-Developer mailing list