OK,

With two layers including 1000 features with nulls, it will create a 
layer with 1 000 000 features.

I think I will deactivate joins on null=null as it has little chance to 
match user's wish.

Michaël


Le 01/12/2016 à 23:32, Rahkonen Jukka (MML) a écrit :
> Hi Michaël,
>
> Yes, there is still a problem if I have NULLs in both layers. It may be that 
> the loop would go to the end finally but it would be only after creating a 
> few million NULL-NULL pairs.
>
> I am not sure if join by NULLs make sense ever. I believe not but at least 
> there could be "ignore nulls" check box. And yes, I was using the internal 
> "Join Table".
>
> -Jukka Rahkonen-
>
> -----Alkuperäinen viesti-----
> Lähettäjä: Michaël Michaud [mailto:m.michael.mich...@orange.fr]
> Lähetetty: 2. joulukuuta 2016 0:16
> Vastaanottaja: jump-pilot-devel@lists.sourceforge.net
> Aihe: Re: [JPP-Devel] Join table can go to eternal loop
>
> Hi Jukka,
>
> I did not understand if you still find there is a problem.
> By the way, are you testing internal "Join Table" which joins two layers 
> using a common attribute ?
>
> For me it works fine. What is questionable is whether one must join two 
> features if they both have null for the join attribute (currently, it does, 
> but I bet a database wouldn't work that way)
>
> Michaël
>
>
> Le 01/12/2016 à 09:31, Rahkonen Jukka (MML) a écrit :
>> More info: I just found that the loop happens exactly because of the NULL 
>> values. I wrote something to fill NULLs and now I can see that I have also 
>> empty values and real multiple matches in the data but those are handled 
>> fine and the result contains "multiple matches" layer.
>>
>> -Jukka-
>> ________________________________________
>> Lähettäjä: Rahkonen Jukka (MML)
>> Lähetetty: 1. joulukuuta 2016 10:24
>> Vastaanottaja: jump-pilot-devel@lists.sourceforge.net
>> Aihe: [JPP-Devel] Join table can go to eternal loop
>>
>> Hi,
>>
>> If Join table function finds several matches it seems to go to an eternal 
>> loop. The status box keeps on flashing "Multiple matches for FID=xxx" and 
>> process does not forward. Fortunately it is possible to kill the process by 
>> pressing the red cross.
>>
>> There is of coarse error in the data but perhaps it could be handled more 
>> friendly. In my case the error was due to NULL values in the connecting 
>> field.
>>
>> -Jukka Rahkonen-
>> ----------------------------------------------------------------------
>> -------- _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>> ----------------------------------------------------------------------
>> -------- _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to