From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Selecting table row with latest date [RESOLVED] |
Date: | 2021-08-19 22:30:24 |
Message-ID: | f9f2e217-5b4a-0c7b-d7c4-f598dea0922e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/19/21 3:07 PM, Rich Shepard wrote:
> On Thu, 19 Aug 2021, David G. Johnston wrote:
>
> David,
>
> I'm not at all surprised as I use postgres infrenquently. Once I have
> queries producing results I need for my business tracking or client data I
> just use them. I'm neither a professional DBA nor database developer and
> use
> a variety of technical applications dependent on project needs.
>
> And I'm quite used to being chastised by those who work primarily with a
> single application all day every day and I accept that I'm not an expert.
Things would go easier if you supplied context with your replies, so:
The exact query that produced a result.
Query results of more then one column so the data itself has context.
Error messages.
Indication of whether the result is what you wanted?
And if it isn't then the expected result.
Then folks could come up with a more complete answer sooner and with
less frustration for all.
>
> Regards,
>
> Rich
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-08-19 22:42:35 | Re: Regexp_replace bug / does not terminate on long strings |
Previous Message | Rich Shepard | 2021-08-19 22:07:37 | Re: Selecting table row with latest date [RESOLVED] |