| From: | Thomas Good <tomg(at)admin(dot)nrnet(dot)org> |
|---|---|
| To: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] Making NULLs visible. |
| Date: | 1998-10-11 20:28:41 |
| Message-ID: | Pine.LNX.3.96.981011161908.11556A-100000@admin.nrnet.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Watching all this go by...as a guy who has to move alot of data
from legacy dbs to postgres, I've gotten used to \N being a null.
My vote, if I were allowed to cast one, would be to have one null
and that would be the COPY command null. I have no difficulty
distinguishing a null from a newline...
At the pgsql command prompt I would find seeing \N rather reassuring.
I've seen alot of these little guys.
---------- Sisters of Charity Medical Center ----------
Department of Psychiatry
----
Thomas Good <tomg(at)q8(dot)nrnet(dot)org>
Coordinator, North Richmond C.M.H.C. Information Systems
75 Vanderbilt Ave, Quarters 8 Phone: 718-354-5528
Staten Island, NY 10304 Fax: 718-354-5056
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andre Luis | 1998-10-11 21:54:20 | |
| Previous Message | Steve Doliov | 1998-10-09 22:18:00 | Re: [GENERAL] Making NULLs visible. |