| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Sergey Ten <sergey(at)sourcelabs(dot)com>, jason(at)sourcelabs(dot)com |
| Subject: | Re: Escape handling in COPY, strings, psql |
| Date: | 2005-05-30 14:18:08 |
| Message-ID: | 429B20A0.5020707@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> I read the PHP addslashes() manual page:
>
> http://us3.php.net/addslashes
>
> First, I see what people mean about PHP having most of the complex
> content in comments, rather than in the actual manual text, and this
> tendency is certainly something we want to avoid --- you end up having
> to digest all the comments to find the details that should be in the
> manual already.
Actually, all the comments are posted on the php-doc list, with
automatic urls in them for 'fixed in cvs', 'rejected', etc.
Each comment is supposed to be acted upon (ie. fixed in source), then
deleted.
There's still a lot of old comment around that hasn't had that treatment
though...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-30 14:19:20 | Re: Escape handling in COPY, strings, psql |
| Previous Message | Bruce Momjian | 2005-05-30 14:12:19 | Re: Escape handling in COPY, strings, psql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-30 14:19:20 | Re: Escape handling in COPY, strings, psql |
| Previous Message | Bruce Momjian | 2005-05-30 14:12:19 | Re: Escape handling in COPY, strings, psql |