Re: [HACKERS] One-shot expanded output in psql using \G
On Fri, Jan 27, 2017 at 11:03:05AM -0500, Stephen Frost wrote: > Well, I did get the impression that you weren't thinking about that, > which is actually kind of surpirsing to me. Lots of things work on "the > current query buffer", which is the last query (successful or not, to be > clear..): > > \crosstabview > \e > \g > \gexec > \gset > \p > \w > \watch > > It's not entirely clear to me why the docs sometimes say "current query > buffer" and somtimes say "current query input buffer". I would expect the "current query input buffer" to be what is used to enter the next query. When you hit enter that goes into the "current query buffer" (as the entered query is now officially complete and thus becomes the current query) and then "current query input buffer" is cleared for the next action to be dealt with, be it a query or psql command. -- "A search of his car uncovered pornography, a homemade sex aid, women's stockings and a Jack Russell terrier." - http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-118083480 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10.0
On Tue, Jun 14, 2016 at 01:38:44PM -0700, Joshua D. Drake wrote:
> On 06/14/2016 12:46 PM, Jim Nasby wrote:
>
> >Any ideas on naming for such a function? version_detail()? I suppose
> >while we're at this we might as well provide the compile details as well.
>
> version(detail) or version(verbose)
If we're looking at forward only changes, is it possible to introduce a
JSONB output to it. Then people can rip out whichever component they want
at will.
For example:
{
"full": 10.0,
"major": 10,
"patchlevel": 0
}
and whatever else may be pertinent. I used numeric types above but they
can be strings if that works better.
We have the capability to provide (semi-)structured data. Might be an idea
to make greater use of it.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
-
http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-118083480
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Feature Request: inline comments
Whilst reading http://www.postgresql.org/docs/8.2/interactive/sql-comment.html I came across this user comment: Ricardo Bánffy 04 Sep 2007 18:15:44 It is a pretty obvious suggestion I bet was made many, many times before, but it would be very useful if you could create comments while creating the objects themselves, like CREATE TABLE FOO ( ID INTEGER NOT NULL PRIMARY KEY COMMENT 'The ID', VALUE VARCHAR(10) COMMENT 'The value', ) COMMENT 'The table'; This would be a good thing as it would make documenting schemas more in-your-face and less prone to forgetting (ie, atm, if you do want to comment on rows you effectively wind up with two table definitions (kinda)). Perhaps this is a small enough add to make it into 8.3? -- To the extent that we overreact, we proffer the terrorists the greatest tribute. - High Court Judge Michael Kirby ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Feature Request: inline comments
On Wed, Nov 07, 2007 at 06:32:53PM -0500, Tom Lane wrote: CaT [EMAIL PROTECTED] writes: It is a pretty obvious suggestion I bet was made many, many times before, but it would be very useful if you could create comments while creating the objects themselves, like CREATE TABLE FOO ( ID INTEGER NOT NULL PRIMARY KEY COMMENT 'The ID', VALUE VARCHAR(10) COMMENT 'The value', ) COMMENT 'The table'; This seems like a fairly bad idea to me, because it converts your table definitions into proprietary syntax. Heaven help you trying to load the above into any other database. With a separate COMMENT ON command, at least you have a fighting chance of ignoring the errors and pressing on. Well, in a dump of the DB, you could have them as COMMENT ON. Otherwise I /think/ this should do it in vim at least: :%s/ COMMENT '\([^']*''\)*[^']*'// It's not a perfect regex (though I think it could be made to hand E'' escaping) but it'll do for most comments. Perhaps this is a small enough add to make it into 8.3? Feature freeze was six months ago, and no this wouldn't be a small add even if it was the best idea since sliced bread. Fair cop. -- To the extent that we overreact, we proffer the terrorists the greatest tribute. - High Court Judge Michael Kirby ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
