From: | Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: default enconding |
Date: | 2004-03-28 01:45:05 |
Message-ID: | m3fzbtsq1q.fsf@conexa.fciencias.unam.mx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> writes:
> > Hi, I have found what I thing is a quite annoying behaviour of
> > Postgres (psql). When you type (and ask for complation) for some
> > string that has some characters not in the ASCII encoding it requires
> > a double quote on it, however if you don't put those double quotes
> > around it, you can still execute the query.
>
> ... in other words, it doesn't require the double quotes. I don't see
> the value of being more restrictive. Why is this annoying?
It's because you can't complete without the double quote, so,
select something.fo<tab>
doesn't complete if you have only foó as the only completion whereas
select something ."fo
does.
Regards,
Manuel.
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2004-03-28 01:50:45 | Re: default enconding |
Previous Message | Tom Lane | 2004-03-28 01:12:09 | Re: default enconding |