From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Formating psql query output |
Date: | 2021-07-19 18:01:22 |
Message-ID: | 8DC70752-D1F1-4841-8E68-C7103764B144@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Jul 19, 2021, at 11:49 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> On 7/19/21 10:33 AM, Rich Shepard wrote:
>> Until I finish building the python/tkinter/psycopg2 front end to my business
>> tracking tool I continue to work using the psql shell.'
>> I have a working .sql script that reports my contacts between two dates; the
>> script returns more columns than I want included in the report. I want to
>> pipe the output through an awk script to extract, in order, the columns I
>> need. I'm stuck at the point of defining options to psql.
>
> Is there a reason you can't just restrict the query to the columns you want?
>
Also had that thought but OP is wise to head the other switches for cleaner output. But also should probably get familiar with to-json options as well for easy pickup on the eventual client.
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2021-07-19 18:53:08 | RE: Formating psql query output |
Previous Message | Adrian Klaver | 2021-07-19 17:49:34 | Re: Formating psql query output |