David Fetter wrote:
> On Thu, Feb 25, 2010 at 07:20:58PM -0500, Bruce Momjian wrote:
> >
> > Did we ever get tab completion support for these backslash commands?
>
> Nope :/
>
> Not sure if I'll be able to get to it this week, either.
What is the TODO description then?
--
Bruce Momjian
On Thu, Feb 25, 2010 at 07:20:58PM -0500, Bruce Momjian wrote:
>
> Did we ever get tab completion support for these backslash commands?
Nope :/
Not sure if I'll be able to get to it this week, either.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Y
Did we ever get tab completion support for these backslash commands?
---
David Fetter wrote:
> On Fri, Apr 17, 2009 at 04:42:31PM -0400, Alvaro Herrera wrote:
> > David Fetter wrote:
> >
> > > Is this any better?
> >
> > S
David Fetter wrote:
> On Mon, Apr 27, 2009 at 01:31:11PM -0400, Alvaro Herrera wrote:
> > Tab completion has never been perfect. I don't think beta is the
> > best time to be improving it so much. I think a small patch that
> > just adds "\dfa", "\dfw" and appropriate pattern completions (i.e.
>
On Mon, Apr 27, 2009 at 01:31:11PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
> > On Mon, Apr 27, 2009 at 01:11:44PM -0400, Tom Lane wrote:
>
> > > It seems like rather a large change to be making in beta. Can
> > > you make a small patch that fixes the immediate problem, and
> > > leave
David Fetter wrote:
> On Mon, Apr 27, 2009 at 01:11:44PM -0400, Tom Lane wrote:
> > It seems like rather a large change to be making in beta. Can you
> > make a small patch that fixes the immediate problem, and leave the
> > refactoring for 8.5?
>
> The hack I've come up with short of the refact
On Mon, Apr 27, 2009 at 01:11:44PM -0400, Tom Lane wrote:
> David Fetter writes:
> > I have a handle on the problem, which is that the tab completion
> > code assumes, wrongly, that it only needs to deal with fixed
> > strings. It's actually been false for some time in the \div case,
> > for exam
David Fetter writes:
> I have a handle on the problem, which is that the tab completion code
> assumes, wrongly, that it only needs to deal with fixed strings. It's
> actually been false for some time in the \div case, for example. The
> S option has shattered the fixed-string assumption.
Check
On Mon, Apr 27, 2009 at 10:39:33AM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
> > On Fri, Apr 17, 2009 at 04:42:31PM -0400, Alvaro Herrera wrote:
>
> > > It also seems like we're missing tab completion support for this.
> >
> > Oops. Working on that now.
>
> Any luck with this?
I have
David Fetter wrote:
> On Fri, Apr 17, 2009 at 04:42:31PM -0400, Alvaro Herrera wrote:
> > It also seems like we're missing tab completion support for this.
>
> Oops. Working on that now.
Any luck with this?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
Postgre
Tom Lane wrote:
> Alvaro Herrera writes:
> > Still, my original proposal was \df[antw][S+]. The extra brackets are
> > obviously redundant, but if we're about providing cues, this is a good
> > cue IMO. It allows the [S+] to match the other lines.
>
> I'm for that too. Bruce was complaining th
Alvaro Herrera writes:
> Still, my original proposal was \df[antw][S+]. The extra brackets are
> obviously redundant, but if we're about providing cues, this is a good
> cue IMO. It allows the [S+] to match the other lines.
I'm for that too. Bruce was complaining that it'd make the column
wide
Tom Lane wrote:
> Bruce Momjian writes:
> > If I can get someone else to say they prefer brackets over parentheses in
> > \? I will make the change. Right now we have:
>
> >\df[antwS+] [PATTERN] list (only agg/normal/trigger/window) functions
>
> > With brackets it would be:
>
> >\df[
Bruce Momjian writes:
> If I can get someone else to say they prefer brackets over parentheses in
> \? I will make the change. Right now we have:
>\df[antwS+] [PATTERN] list (only agg/normal/trigger/window) functions
> With brackets it would be:
>\df[antwS+] [PATTERN] list [only agg/
to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, Apr 22, 2009 at 08:32:20AM -0400, Bruce Momjian wrote:
>
> [...]
>
> > True, but the problem is that the brackets don't correspond [...]
>
> Yes, right. Still, square brackets seem (to me) to provide some visu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 22, 2009 at 08:32:20AM -0400, Bruce Momjian wrote:
[...]
> True, but the problem is that the brackets don't correspond [...]
Yes, right. Still, square brackets seem (to me) to provide some visual
cue. But I admit that this is already adv
to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, Apr 21, 2009 at 01:26:33PM -0400, Bruce Momjian wrote:
>
> [...]
>
> > I merged the entries into one line:
> >
> > \df[antwS+] [PATTERN] list (only agg/normal/trigger/window) functions
> >
> > I didn't f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 21, 2009 at 01:26:33PM -0400, Bruce Momjian wrote:
[...]
> I merged the entries into one line:
>
> \df[antwS+] [PATTERN] list (only agg/normal/trigger/window) functions
>
> I didn't feel I had room to do [][] like Alvaro suggeste
David Fetter wrote:
> On Tue, Apr 21, 2009 at 01:04:44PM -0400, Alvaro Herrera wrote:
> > David Fetter wrote:
> >
> > > Oh, and I forgot to send some error-handling and cleanup code per
> > > Alvaro. Please find attached. :)
> >
> > Declarations before code please.
>
> Fixed patch attached.
Ap
Alvaro Herrera wrote:
> Kevin Grittner wrote:
> > Bruce Momjian wrote:
> >
> > > \df[S+] [PATTERN] list functions
> > > \df[antwS+] [PATTERN] list only agg/normal/trigger/window functions
> >
> > Shouldn't that second line have some curly braces? Like maybe:
> >
> > \df{antw}[S+] [PAT
On Tue, Apr 21, 2009 at 01:04:44PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
>
> > Oh, and I forgot to send some error-handling and cleanup code per
> > Alvaro. Please find attached. :)
>
> Declarations before code please.
Fixed patch attached.
Cheers,
David.
--
David Fetter http://
"Kevin Grittner" writes:
> Bruce Momjian wrote:
>> The problem is I don't see curly braces used anywhere in \?
> I see it in 8.3:
> : \d{t|i|s|v|S} [PATTERN] (add "+" for more detail)
> :list tables/indexes/sequences/views/system tables
Yeah. The only reason that \d[tisv] do
David Fetter wrote:
> Oh, and I forgot to send some error-handling and cleanup code per
> Alvaro. Please find attached. :)
Declarations before code please.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via
On Tue, Apr 21, 2009 at 09:33:26AM -0700, David Fetter wrote:
> On Tue, Apr 21, 2009 at 09:26:13AM -0700, Joshua D. Drake wrote:
> > On Tue, 2009-04-21 at 12:19 -0400, Alvaro Herrera wrote:
> >
> > > I suggested this to Bruce over IM:
> > >
> > > \df[antw][S+] list [only agg/normal/trigger/wi
Bruce Momjian wrote:
> The problem is I don't see curly braces used anywhere in \?
I see it in 8.3:
: \d{t|i|s|v|S} [PATTERN] (add "+" for more detail)
:list tables/indexes/sequences/views/system tables
and:
: \pset NAME [VALUE]
:set table output option
:
Alvaro Herrera wrote:
> \df[antw][S+] list [only agg/normal/trigger/window] functions
>
> (one line only, removing the second redundant line). This seems
> clea[nr]er to me. Bruce says it would confuse users.
That's clear to me, anyway (if you include PATTERN). I'd be fine with
it or
On Tue, Apr 21, 2009 at 09:26:13AM -0700, Joshua D. Drake wrote:
> On Tue, 2009-04-21 at 12:19 -0400, Alvaro Herrera wrote:
>
> > I suggested this to Bruce over IM:
> >
> > \df[antw][S+] list [only agg/normal/trigger/window] functions
> >
> > (one line only, removing the second redundant lin
Kevin Grittner wrote:
> Bruce Momjian wrote:
>
> > \df[S+] [PATTERN] list functions
> > \df[antwS+] [PATTERN] list only agg/normal/trigger/window functions
>
> Shouldn't that second line have some curly braces? Like maybe:
>
> \df{antw}[S+] [PATTERN] list only agg/normal/trigger/wind
On Tue, 2009-04-21 at 12:19 -0400, Alvaro Herrera wrote:
> I suggested this to Bruce over IM:
>
> \df[antw][S+] list [only agg/normal/trigger/window] functions
>
> (one line only, removing the second redundant line). This seems
> clea[nr]er to me. Bruce says it would confuse users. But re
Kevin Grittner wrote:
> Bruce Momjian wrote:
>
> > \df[S+] [PATTERN] list functions
> > \df[antwS+] [PATTERN] list only agg/normal/trigger/window functions
>
> Shouldn't that second line have some curly braces? Like maybe:
>
> \df{antw}[S+] [PATTERN] list only agg/normal/trigger/wind
Bruce Momjian wrote:
> \df[S+] [PATTERN] list functions
> \df[antwS+] [PATTERN] list only agg/normal/trigger/window functions
Shouldn't that second line have some curly braces? Like maybe:
\df{antw}[S+] [PATTERN] list only agg/normal/trigger/window functions
Technically, it should
David Fetter wrote:
> On Wed, Apr 15, 2009 at 08:54:10PM -0400, Alvaro Herrera wrote:
> > David Fetter wrote:
> >
> > > > > I think it's good to have them translatable. As for using "aggregate"
> > > > > instead of "agg" I don't think it's that great an idea. If you need
> > > > > to
> > > > >
On Fri, Apr 17, 2009 at 04:42:31PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
>
> > Is this any better?
>
> So what happens if I do \dfaQ? It should throw an error, yes?
Interesting question.
>
> This help line:
>
> > + fprintf(output, _(" \\df[S+] [PATTERN] list functions. A
On Fri, Apr 17, 2009 at 04:42:31PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
>
> > Is this any better?
>
> So what happens if I do \dfaQ? It should throw an error, yes?
>
> This help line:
>
> > + fprintf(output, _(" \\df[S+] [PATTERN] list functions. Add a, n,
> > t, w for
David Fetter wrote:
> Is this any better?
So what happens if I do \dfaQ? It should throw an error, yes?
This help line:
> + fprintf(output, _(" \\df[S+] [PATTERN] list functions. Add a, n,
> t, w for aggregate, normal, trigger, window\n"));
needs shortening to below 80 chars (or m
David Fetter wrote:
> On Wed, Apr 15, 2009 at 08:54:10PM -0400, Alvaro Herrera wrote:
> > The "translator: " comment needs to be in the line just above the
> > string.
>
> Is this any better?
Yeah, this one is good (as far as this very minor detail is concerned anyway)
--
Alvaro Herrera
On Wed, Apr 15, 2009 at 08:54:10PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
>
> > > > I think it's good to have them translatable. As for using "aggregate"
> > > > instead of "agg" I don't think it's that great an idea. If you need to
> > > > notify translators that "agg" stands for "a
David Fetter wrote:
> > > I think it's good to have them translatable. As for using "aggregate"
> > > instead of "agg" I don't think it's that great an idea. If you need to
> > > notify translators that "agg" stands for "aggregate", add a
> > > /* translator: */ comment.
The "translator: " comm
On Tue, Apr 14, 2009 at 03:18:06PM -0700, David Fetter wrote:
> On Tue, Apr 14, 2009 at 02:52:32PM -0400, Alvaro Herrera wrote:
> > Tom Lane wrote:
> >
> > > I had a second thought about that: presumably we should make the
> > > function type names translatable. If we do that, it might be better
On Tue, Apr 14, 2009 at 02:52:32PM -0400, Alvaro Herrera wrote:
> Tom Lane wrote:
>
> > I had a second thought about that: presumably we should make the
> > function type names translatable. If we do that, it might be better
> > to make the aggregate case be "aggregate" and take the width hit.
>
On Tue, Apr 14, 2009 at 03:04:55PM -0400, Alvaro Herrera wrote:
> David Fetter wrote:
> > On Tue, Apr 14, 2009 at 02:52:32PM -0400, Alvaro Herrera wrote:
>
> > > I think it's good to have them translatable. As for using
> > > "aggregate" instead of "agg" I don't think it's that great an
> > > ide
David Fetter wrote:
> On Tue, Apr 14, 2009 at 02:52:32PM -0400, Alvaro Herrera wrote:
> > I think it's good to have them translatable. As for using
> > "aggregate" instead of "agg" I don't think it's that great an idea.
> > If you need to notify translators that "agg" stands for "aggregate",
> >
On Tue, Apr 14, 2009 at 02:52:32PM -0400, Alvaro Herrera wrote:
> Tom Lane wrote:
>
> > I had a second thought about that: presumably we should make the
> > function type names translatable. If we do that, it might be
> > better to make the aggregate case be "aggregate" and take the
> > width hit
Tom Lane wrote:
> I had a second thought about that: presumably we should make the
> function type names translatable. If we do that, it might be better
> to make the aggregate case be "aggregate" and take the width hit.
> Otherwise translators are going to be puzzled when they come across
> "agg
On Tue, Apr 14, 2009 at 12:35:21PM -0400, Tom Lane wrote:
> David Fetter writes:
> > On Mon, Apr 13, 2009 at 07:24:31PM -0400, Tom Lane wrote:
> >> I'd go for something like
> >>
> >> Type
> >>
> >> window
> >> agg
> >> trigger
> >> normal
> >>
> >> Or we could spell out "aggregate", but that m
David Fetter writes:
> On Mon, Apr 13, 2009 at 07:24:31PM -0400, Tom Lane wrote:
>> I'd go for something like
>>
>> Type
>>
>> window
>> agg
>> trigger
>> normal
>>
>> Or we could spell out "aggregate", but that makes the column a
>> couple of characters wider ...
> Done.
I had a second thoug
On Mon, Apr 13, 2009 at 07:24:31PM -0400, Tom Lane wrote:
> David Fetter writes:
> > Here's a patch that adds a "Function Type" column to \df while
> > removing the now-redundant \da.
>
> Removing \da altogether was nowhere in the consensus, or even in the
> discussion AFAIR.
It's back.
> Also,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Here's a patch that adds a "Function Type" column to \df while
> removing the now-redundant \da.
1. How does it make it redundant - is there a way to view all
aggregates with \df now?
2. Even if the above is satisfied, I think we need a litt
David Fetter writes:
> Here's a patch that adds a "Function Type" column to \df while
> removing the now-redundant \da.
Removing \da altogether was nowhere in the consensus, or even in the
discussion AFAIR. Also, what is the point of using single-letter
type codes when you've made the column hea
Folks,
Here's a patch that adds a "Function Type" column to \df while
removing the now-redundant \da.
Cheers,
David.
--
David Fetter http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fet...@gmail.com
Remember to vote!
Consider donat
50 matches
Mail list logo
