Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Hi, Rémi, there won't be 3.2.4 The next 3.x release will be 3.4.0 (3.2 is no longer maintained). The fix will then be in 3.4 HarrissouLe 20 sept. 2018 8:37 AM, Rémi Desgrange a écrit : > > Oh, I didn’t saw it thank you!! So, for our end user, we can expect this fix > to be present in qgis 3.2.4? > > This is a super great news > > Cheers, Rémi Desgrange > > > Le 19/09/2018 18:35, « Qgis-user au nom de Jürgen E. Fischer » > a écrit : > > Hi Rémi, > > On Wed, 19. Sep 2018 at 14:55:01 +, Rémi Desgrange wrote: > > I’m on mac so, not so easy, but I’ll definitely try on 3.2.3. > > That won't help - the fix is in master (also referenced in the ticket). > > > Jürgen > > -- > Jürgen E. Fischer norBIT GmbH Tel. > +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstraße 13 Fax. > +49-4931-918175-50 > Software Engineer D-26506 Norden > http://www.norbit.de > QGIS release manager (PSC) Germany IRC: jef on > FreeNode > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Oh, I didn’t saw it thank you!! So, for our end user, we can expect this fix to be present in qgis 3.2.4? This is a super great news Cheers, Rémi Desgrange Le 19/09/2018 18:35, « Qgis-user au nom de Jürgen E. Fischer » a écrit : Hi Rémi, On Wed, 19. Sep 2018 at 14:55:01 +, Rémi Desgrange wrote: > I’m on mac so, not so easy, but I’ll definitely try on 3.2.3. That won't help - the fix is in master (also referenced in the ticket). Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Hi Rémi, On Wed, 19. Sep 2018 at 14:55:01 +, Rémi Desgrange wrote: > I’m on mac so, not so easy, but I’ll definitely try on 3.2.3. That won't help - the fix is in master (also referenced in the ticket). Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: PGP signature norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Aurich HRB 100827 Datenschutzerklaerung: https://www.norbit.de/83/ ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
I’m on mac so, not so easy, but I’ll definitely try on 3.2.3. I found some minor change in github repo between final_3_2 branch and master but cannot compare 3.2.3 tags with master to what postgres/db driver/vector layer was modified since 3.2.2. Cordialement, Rémi Desgrange Le 19/09/2018 16:12, « Qgis-user au nom de Jürgen E. Fischer » a écrit : Hi Rémi, On Wed, 19. Sep 2018 at 14:09:16 +, Rémi Desgrange wrote: > Thanks. Already tried that, but didn’t work ☹ Try latest master. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Hi Rémi, On Wed, 19. Sep 2018 at 14:09:16 +, Rémi Desgrange wrote: > Thanks. Already tried that, but didn’t work ☹ Try latest master. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: PGP signature norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Aurich HRB 100827 Datenschutzerklaerung: https://www.norbit.de/83/ ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Thanks. Already tried that, but didn’t work ☹ I think that the real question here is: why Qgis think that my column is text and not uuid? (it try to make ILIKE on the uuid it doesn’t make sense) Sincerly, Rémi Desgrange Le 19/09/2018 15:34, « Qgis-user au nom de Karl Magnus Jönsson » a écrit : Hi. I think I've done something similar. Not against a view though. I had to set the default value for the filed in the form to uuid() to make it work properly. Worth a try. Karl-Magnus Jönsson -Ursprungligt meddelande- Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För Bernhard Ströbl Skickat: den 19 september 2018 15:23 Till: qgis-user@lists.osgeo.org Ämne: Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views Am 19.09.2018 um 11:26 schrieb Rémi Desgrange: > Hi, > > I have some database view used in qgis. (from postgresql 10, postgis2.4). Since some time now (I posted a bug report 3 months ago here: https://issues.qgis.org/issues/19180) This was about errors in my DBs log about selection request that does not end well. But, at this time it was not a problem for the end user. Yesterday, we spotted a much more problematic error. Here is the story: > > We wanted to cut a linestring, so we use the tool “Split Features”. And when we did that. It cut the linestring, so changing the geometry of the linestring (updating) and trying to create a new one with the other part. The problem is: it updated correctly the existing feature, but did _not_ save the other one (it created it in qgis though). Was there any error message from the DB? > The reason behind this is qgis treating an uuid like a text field. So, when treating uuid as text, when it tries to create a new feature out of the old one split, it put the value _1 which cannot work obviously. It is the user's obligation to fill meaningful values in fields. This is e.g. also true for integer primary key fields: if you fill in a value already present or no value at all the changes cannot be saved. I would create an insert trigger on the DB that creates a uuid for any insert request. Hope this hleps Bernhard > > This is not a problem with form or style, the field as the type uuid in qgis, I “mapped” uuid generator on it, and tried text editor too. > > > I don’t know if it’s us that don’t know how to properly configure Qgis or if it’s a bug… > > > Cordialement, Rémi Desgrange > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > __ Information from ESET Mail Security, version of virus signature database 18077 (20180919) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Error from the db : When the linestring is cut: Erroneous query: SELECT "tab_id"::text FROM (SELECT DISTINCT "expl_id" FROM "projet"."v_example" WHERE "expl_id" ILIKE '%97b99098-3807-4d5f-97e9-c58bfff18f68%' ORDER BY "expl_id") foo returned 7 [ERREUR: l'opérateur n'existe pas : uuid ~~* unknown LINE 1: ...expl_id" FROM "projet"."v_example" WHERE "expl_id" ILIKE '%97... And when you try to save: (sorry in French) ERREUR: syntaxe en entrée invalide pour le type uuid : « e5e03331-74cf-4077-92b2-6f93c98c57f6_1 » which should translate to « invalid input syntax from uuid type ». I should mention clearly (if it was not in my first mail) that I tried multiple strategies about widget type in attributes form (text, uuid generator) with both default value and non-default value (expl_id is autogenerated via a default constraint in PG). The thing that really bother me is that it works all fine with the table but not with the view. Cheers, Rémi Desgrange Le 19/09/2018 15:22, « Qgis-user au nom de Bernhard Ströbl » a écrit : Am 19.09.2018 um 11:26 schrieb Rémi Desgrange: > Hi, > > I have some database view used in qgis. (from postgresql 10, postgis2.4). Since some time now (I posted a bug report 3 months ago here: https://issues.qgis.org/issues/19180) This was about errors in my DBs log about selection request that does not end well. But, at this time it was not a problem for the end user. Yesterday, we spotted a much more problematic error. Here is the story: > > We wanted to cut a linestring, so we use the tool “Split Features”. And when we did that. It cut the linestring, so changing the geometry of the linestring (updating) and trying to create a new one with the other part. The problem is: it updated correctly the existing feature, but did _not_ save the other one (it created it in qgis though). Was there any error message from the DB? > The reason behind this is qgis treating an uuid like a text field. So, when treating uuid as text, when it tries to create a new feature out of the old one split, it put the value _1 which cannot work obviously. It is the user's obligation to fill meaningful values in fields. This is e.g. also true for integer primary key fields: if you fill in a value already present or no value at all the changes cannot be saved. I would create an insert trigger on the DB that creates a uuid for any insert request. Hope this hleps Bernhard > > This is not a problem with form or style, the field as the type uuid in qgis, I “mapped” uuid generator on it, and tried text editor too. > > > I don’t know if it’s us that don’t know how to properly configure Qgis or if it’s a bug… > > > Cordialement, Rémi Desgrange > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > __ Information from ESET Mail Security, version of virus signature database 18077 (20180919) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Hi. I think I've done something similar. Not against a view though. I had to set the default value for the filed in the form to uuid() to make it work properly. Worth a try. Karl-Magnus Jönsson -Ursprungligt meddelande- Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För Bernhard Ströbl Skickat: den 19 september 2018 15:23 Till: qgis-user@lists.osgeo.org Ämne: Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views Am 19.09.2018 um 11:26 schrieb Rémi Desgrange: > Hi, > > I have some database view used in qgis. (from postgresql 10, postgis2.4). > Since some time now (I posted a bug report 3 months ago here: > https://issues.qgis.org/issues/19180) This was about errors in my DBs log > about selection request that does not end well. But, at this time it was not > a problem for the end user. Yesterday, we spotted a much more problematic > error. Here is the story: > > We wanted to cut a linestring, so we use the tool “Split Features”. And when > we did that. It cut the linestring, so changing the geometry of the > linestring (updating) and trying to create a new one with the other part. The > problem is: it updated correctly the existing feature, but did _not_ save the > other one (it created it in qgis though). Was there any error message from the DB? > The reason behind this is qgis treating an uuid like a text field. So, when > treating uuid as text, when it tries to create a new feature out of the old > one split, it put the value _1 which cannot work obviously. It is the user's obligation to fill meaningful values in fields. This is e.g. also true for integer primary key fields: if you fill in a value already present or no value at all the changes cannot be saved. I would create an insert trigger on the DB that creates a uuid for any insert request. Hope this hleps Bernhard > > This is not a problem with form or style, the field as the type uuid in qgis, > I “mapped” uuid generator on it, and tried text editor too. > > > I don’t know if it’s us that don’t know how to properly configure Qgis or if > it’s a bug… > > > Cordialement, Rémi Desgrange > > > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > __ Information from ESET Mail Security, version of virus signature database 18077 (20180919) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Am 19.09.2018 um 11:26 schrieb Rémi Desgrange: Hi, I have some database view used in qgis. (from postgresql 10, postgis2.4). Since some time now (I posted a bug report 3 months ago here: https://issues.qgis.org/issues/19180) This was about errors in my DBs log about selection request that does not end well. But, at this time it was not a problem for the end user. Yesterday, we spotted a much more problematic error. Here is the story: We wanted to cut a linestring, so we use the tool “Split Features”. And when we did that. It cut the linestring, so changing the geometry of the linestring (updating) and trying to create a new one with the other part. The problem is: it updated correctly the existing feature, but did _not_ save the other one (it created it in qgis though). Was there any error message from the DB? The reason behind this is qgis treating an uuid like a text field. So, when treating uuid as text, when it tries to create a new feature out of the old one split, it put the value _1 which cannot work obviously. It is the user's obligation to fill meaningful values in fields. This is e.g. also true for integer primary key fields: if you fill in a value already present or no value at all the changes cannot be saved. I would create an insert trigger on the DB that creates a uuid for any insert request. Hope this hleps Bernhard This is not a problem with form or style, the field as the type uuid in qgis, I “mapped” uuid generator on it, and tried text editor too. I don’t know if it’s us that don’t know how to properly configure Qgis or if it’s a bug… Cordialement, Rémi Desgrange ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user __ Information from ESET Mail Security, version of virus signature database 18077 (20180919) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] [Possible bug] Qgis treating uuid as text in db views
Hi, I have some database view used in qgis. (from postgresql 10, postgis2.4). Since some time now (I posted a bug report 3 months ago here: https://issues.qgis.org/issues/19180) This was about errors in my DBs log about selection request that does not end well. But, at this time it was not a problem for the end user. Yesterday, we spotted a much more problematic error. Here is the story: We wanted to cut a linestring, so we use the tool “Split Features”. And when we did that. It cut the linestring, so changing the geometry of the linestring (updating) and trying to create a new one with the other part. The problem is: it updated correctly the existing feature, but did _not_ save the other one (it created it in qgis though). The reason behind this is qgis treating an uuid like a text field. So, when treating uuid as text, when it tries to create a new feature out of the old one split, it put the value _1 which cannot work obviously. This is not a problem with form or style, the field as the type uuid in qgis, I “mapped” uuid generator on it, and tried text editor too. I don’t know if it’s us that don’t know how to properly configure Qgis or if it’s a bug… Cordialement, Rémi Desgrange ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
