Re: Unable to match same value in field.

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Condor <condor(at)stz-bg(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to match same value in field.
Date: 2016-03-12 18:44:02
Message-ID: 56E46372.7090605@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/12/2016 08:11 AM, Condor wrote:
Ccing list

>>>> On 03/10/2016 01:09 AM, Condor wrote:

>>
>>> Process that populate them isnt the same but data is coming from
>>> database not from user input filed.
>>>
>>> Any ideas ?
>>
>> Not at the moment, but some unanswered questions:
>>
>> Is '284110000123315' the only value you are having issues with?
>
> Yes, I now make some tests, it's seems that is the only value that make
> troubles.
>
>>
>> What happens if you populate the field in list_cards_tbl with
>> the data from list_newcards_tbl?
>>
>
> Everything is work. I update value with '284110000123315' manual (I just
> select value with like and update it) and then rerun query and server
> now found that data.
> Yes, I can do that in first moment but was very strange for me why after
> rebuild value still cant be find when md5 and bit_length prove that is
> the same string.

I do not know, that is why I Cced list, maybe someone else has an idea.

>
> Any way, problem solved.
>
> HS
>
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2016-03-12 20:33:33 Q: extract database name from directory dump
Previous Message Peter J. Holzer 2016-03-12 18:43:38 Re: index problems (again)