From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, David Christensen <david(at)endpoint(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: MySQL-ism help patch for psql |
Date: | 2010-01-20 15:11:11 |
Message-ID: | 873a20erqo.fsf@hi-media-techno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> If what the user wanted was to be using MySQL, he is out of luck
> anyway.
That's not what we're talking about. We're talking about having a nice
client tool for those people having to do both MySQL and PostgreSQL
support, or new to PostgreSQL and comming from MySQL.
I'll give my vote to Peter's idea that show tables; should better act as
if you typed \d.
I don't see what the gain is to refuse being nice to MySQL newcomers
when someone actually does the work. If the USE keyword is one we want
to keep free for our own usage, let just skip that compat option.
> I'm actually no big advocate of the \d commands. They're basically
> magical queries that you can't easily see or edit
We already have the psql \set ECHO_HIDDEN command to easily see the
query, then it's a copy/paste away. I'd propose to have this setting
also make it so that the query it runs is placed in the buffer for next
\e command, which is not the case in 8.4.
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-01-20 15:13:01 | Re: Git out of sync vs. CVS |
Previous Message | Boszormenyi Zoltan | 2010-01-20 15:00:36 | Re: lock_timeout GUC patch |