| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: multi line text data/query ?bug? |
| Date: | 2005-03-24 14:46:59 |
| Message-ID: | 26478.1111675619@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> IMHO, if you're trying to write portably, don't just hit enter when you
> want an end of line, use \n or \r to indicate *exactly* what you mean.
Indeed. We are already permissive about line endings in SQL text, so
this discussion really boils down only to whether we should reinterpret
data that's inside a string literal. There are good style reasons why
you should never put an unescaped newline into a string literal in the
first place ... and if you do, I don't think it's the database's job to
second-guess what you meant.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | GIROIRE Nicolas (COFRAMI) | 2005-03-24 14:49:38 | sort array optimisation in pl/perl |
| Previous Message | Robert Treat | 2005-03-24 14:44:09 | Re: Good Books |