Re: new unicode table border styles for psql

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: new unicode table border styles for psql
Date: 2013-11-25 15:26:55
Message-ID: m21u244i4g.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> I'm sorry, but I don't understand how off-topic or hijack applies here.

And I just realize there's another way to read what Pavel said, which is
that *user scripts* parsing the output of psql might become harder to
write as soon as they don't control the default border style in use.

Well in that case, yes I'm vastly off-topic.

I was answering to how to parse the user setting itself, so writing C
code inside the psql source tree itself, and how to expose a fine
grained solution to that problem without having to write a whole new
configuration parser.

> It just seems to me to be a very big stretch to go from the topic of psql
> border styles to the topic of psql scripting support. Your use case would
> surely be using a sledgehammer to crack a nut. By all means argue for better
> scripting support in psql, but I would suggest your argument would be better
> if the use case were something more important and central to psql's purpose.

I think I just understood something entirely different that what you
were talking about.

--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-11-25 15:27:08 Re: docbook-xsl version for release builds
Previous Message Andrew Dunstan 2013-11-25 15:17:06 Re: new unicode table border styles for psql