| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Brad White <b55white(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: garbage data back |
| Date: | 2023-03-06 21:56:06 |
| Message-ID: | 4680520c-2452-7458-aab6-99943074a443@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/6/23 1:27 PM, Brad White wrote:
> In that picture, it's clear what is happening.
> Here, again, is the result that had me stumped.
> image.png
> What threw me was that the field I was looking for had the format of
> 6d-4d and this field appeared to have the same format.
> But once you expand it, you can see that it has a 6d-7d format and isn't
> the field I'm looking for at all. I was trying to take a shortcut by
> finding the data in the table instead of digging in and looking up what
> field was used in the report. And it appeared at first that I had found
> it. ¯\_(?)_/¯
psql is your friend.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Clements | 2023-03-06 22:06:27 | Idea: PostgreSQL equivalent to Oracle's KEEP clause |
| Previous Message | Brad White | 2023-03-06 21:27:29 | Re: garbage data back |