|
Re: psql -F problems: msg#00109db.postgresql.bugs
Hubert depesz Lubaczewski writes: > i belive this kind of information - given from command line - should be > parsed again in psql itself - just like it is parsed when you enter > something at psql prompt. The command line parser inside psql works pretty much like a Unix shell. That means quoting and escaping is resolved *before* the arguments are passed to the command. So when you enter \f '\t' then the parser resolves this as two tokens: the first is <backslash><f> and the second is <tab character>. The \f command and ultimately the routine that sets the field separator have nothing to do with that. I believe this design is ok, even though it creates apparent inconsistencies. If you make it behave like you appear to imagine, then you need to double-escape certain characters in situations where other users might not expect it. -- Peter Eisentraut peter_e@xxxxxxx ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: psql -F problems: 00109, Tom Lane |
|---|---|
| Next by Date: | Re: [SQL] 7.3 GROUP BY differs from 7.2: 00109, Josh Berkus |
| Previous by Thread: | Re: psql -F problemsi: 00109, Tom Lane |
| Next by Thread: | Re: psql -F problems: 00109, Llew Sion Goodstadt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |