| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Shouldn't pg_settings.enumvals be array of text? |
| Date: | 2008-10-06 14:15:11 |
| Message-ID: | 3221.1223302511@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Agreed, it can certainly be bettered. text[] seems to be the cleanest,
> but then we still have the issue with wide output in psql, no? But
> should we really design the view around the single use-case of psql? You
> can still just omit that column from the SELECT if you want...
Well, if we present as text[] then someone could easily use
array_to_string to format the column the other way. So probably
text[] is the right thing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-10-06 14:24:04 | Re: Shouldn't pg_settings.enumvals be array of text? |
| Previous Message | Magnus Hagander | 2008-10-06 14:08:06 | Re: Shouldn't pg_settings.enumvals be array of text? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-10-06 14:24:04 | Re: Shouldn't pg_settings.enumvals be array of text? |
| Previous Message | Magnus Hagander | 2008-10-06 14:08:06 | Re: Shouldn't pg_settings.enumvals be array of text? |