| From: | Chris Angelico <rosuav(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: problem with distinct not distincting... |
| Date: | 2012-10-17 22:13:07 |
| Message-ID: | CAPTjJmo6=Qa2BXOL2YsAFnBQmUvhMRH1q25HonwMQz+NRaT5rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 18, 2012 at 2:32 AM, John Beynon <john(at)kyan(dot)com> wrote:
> I just managed to solve the problem infact.
>
> The trailing 'e' character on the name was different for one row. All
> my tools, (pgadmin and the source data in openoffice) showed the same
> 'e' character but psql showed it as different character...
>
> Thanks for all taking the time to read / answer. It stumped me for a while!
Cool! That's where the sanity check Merlin suggested comes in really
handy. You can manually key in what you think it's showing, and
compare with the two rows:
sikorsky(at)sikorsky:~$ psql -c "select md5('Roaccutane')"
md5
----------------------------------
70f818454267c719ed612f50fe563f64
(1 row)
Anything that shows a different hash is clearly different... somehow.
ChrisA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-10-17 22:50:34 | Re: allow servers to access to the same data |
| Previous Message | Daniel Serodio (lists) | 2012-10-17 21:35:54 | Re: allow servers to access to the same data |