Re: Unicode UTF-8 table formatting for psql text output
Greg Stark <gsstark@mit.edu>
From: Greg Stark <gsstark@mit.edu>
To: Roger Leigh <rleigh@codelibre.net>
Cc: Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2009-10-26T17:12:05Z
Lists: pgsql-hackers
2009/10/25 Roger Leigh <rleigh@codelibre.net>: > rleigh=# \l > List of databases > Name │ Owner │ Encoding │ Collation │ Ctype │ Access privileges > ─────────────────┼──────────┼──────────┼─────────────┼─────────────┼─────────────────────── > merkelpb │ rleigh │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ > postgres │ postgres │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ > projectb │ rleigh │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ > rleigh │ rleigh │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ > […] > template0 │ postgres │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ =c/postgres ↵ > │ │ │ │ │ postgres=CTc/postgres > template1 │ postgres │ UTF8 │ en_GB.UTF-8 │ en_GB.UTF-8 │ =c/postgres ↵ > │ │ │ │ │ postgres=CTc/postgres > […] > (17 rows) > While i agree this looks nicer I wonder what it does to things like excel/gnumeric/ooffice auto-recognizing table layouts and importing files. I'm not sure our old format was so great for this so maybe this is actually an improvement I'm asking for. But as long as we're changing the format... It would at at least be good to test the behaviour -- greg