| From: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
|---|---|
| To: | <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | <peter_e(at)gmx(dot)net>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Quoting of psql \d output |
| Date: | 2003-12-23 17:04:44 |
| Message-ID: | 3053.62.158.111.153.1072199084.squirrel@new.host.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian writes:
> But it isn't a message:
>
> Table "public.xx"
> Column | Type | Modifiers
> --------+---------+-----------
> y | integer |
> Indexes:
> "ii" btree (y)
By definition, everything that is printed out for human consumption is a
message.
Everything that is printed out for consumption by an SQL parser (e.g., in
pg_dump) is encouraged to use SQL quoting rules. But everything that is
intended to be read by humans should use quoting rules that are common in
real-life publishing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-12-23 17:12:11 | Re: Quoting of psql \d output |
| Previous Message | Mark Feit | 2003-12-23 16:12:26 | (Mis?)Behavior of \copy with -f and \i |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-12-23 17:12:11 | Re: Quoting of psql \d output |
| Previous Message | Bruce Momjian | 2003-12-23 16:02:12 | Re: Quoting of psql \d output |