From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql UPDATE field [tab] expands to DEFAULT? |
Date: | 2019-06-18 00:22:53 |
Message-ID: | ee3b2dfa-5f37-b134-90f2-a2455a6f4b08@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 6/17/19 4:33 PM, Ken Tanzer wrote:
> On Mon, Jun 17, 2019 at 4:24 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 6/17/19 3:03 PM, Ken Tanzer wrote:
> >
> > So I'm curious if this is intended behavior, if it's considered
> useful,
> > and/or if it's a placeholder for something in the future that
> will be
> > useful. Also, is this new, as I've never noticed it before?
>
> Not sure how long that has been around.
>
> My cheat for dealing with many/long column names is:
>
>
> Thanks Adrian, though I wasn't really seeking tips for column names. I
> was instead trying to understand whether this particular tab expansion
> was intentional and considered useful, and if so what that usefulness
If I am following the below correctly it is intentional:
Line 2888
Useful, that is in the eye of the beholder:)
> was, because it's rather escaping me!
>
> Cheers,
> Ken
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2019-06-18 00:23:47 | Re: psql UPDATE field [tab] expands to DEFAULT? |
Previous Message | Tim Cross | 2019-06-18 00:09:11 | Re: psql UPDATE field [tab] expands to DEFAULT? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2019-06-18 00:23:47 | Re: psql UPDATE field [tab] expands to DEFAULT? |
Previous Message | Tim Cross | 2019-06-18 00:09:11 | Re: psql UPDATE field [tab] expands to DEFAULT? |