| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | The Aztechian <jaym(at)aztech-cs(dot)com> |
| Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, pgsql-ports(at)postgreSQL(dot)org |
| Subject: | Re: [PORTS] Port Bug Report: Can't import nullable date field with COPY in psql |
| Date: | 1999-02-01 14:10:48 |
| Message-ID: | 36B5B5E8.2BB051E6@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-ports |
> > > Null in copy is input using \N. See copy manual page.
> > No offense intended, but that is *certainly* not obvious in the man
> > page, as far as an *input* situation goes. The man page for copy
> > discusses the format of output files. Who do I contact with
> > suggestions for the man pages? Would that be Douglas J. Dunlop?
Douglas is not active in any Postgres support (and has not been for
quite some time). Where did you find the reference to him?
Also, we will eventually supplant the current man pages with text
derived from ref/copy.sgml, so if you want to suggest changes, fixes, or
improvements to the docs (or even better, submit patches! :) please look
there too.
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Unprivileged user | 1999-02-01 15:27:40 | Port Bug Report: Cache lookup Failure |
| Previous Message | Thomas G. Lockhart | 1999-02-01 13:47:56 | Re: [PORTS] Port Bug Report: CURRENT_DATE problem |