| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pad column with leading zeros or space |
| Date: | 2002-01-23 16:51:03 |
| Message-ID: | 3226.1011804663@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> writes:
> I am trying to create a table where I need to pad certain
> columns. ...
> Yeah, well, I don't know why a delimited format wouldn't
> help the clients, but it seems that they've hardcode
> their process so that the text dump will look *exactly*
> as specified.
Rather than hacking the database representation into some unnatural
choice of datatypes, I'd suggest you keep the table declaration clean
and work on producing the requested output format during the dump.
A simple sed, awk, or Perl script to postprocess a dump file might
well be the cleanest answer.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-23 17:08:44 | Re: postgresql 7.2b5 and vserver: statistics sockets |
| Previous Message | postgresql | 2002-01-23 16:48:14 | Re: postgresql 7.2b5 and vserver: statistics sockets |