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. So what about changing the
behaviour to either don't accept characters with the 8 bit set or
accept by default strings in the iso-8859-1 encoding instead of ASCII
endoding by default.

Regards,
Manuel.


27 Mar 2004 18:56:45 -0600
Manuel Sugawara <masm@fciencias.unam.mx>
default enconding
Manuel Sugawara <masm@fciencias.unam.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?

			regards, tom lane

Sat, 27 Mar 2004 20:12:09 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: default enconding 
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Manuel Sugawara <masm@fciencias.unam.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.

27 Mar 2004 19:45:05 -0600
Manuel Sugawara <masm@fciencias.unam.mx>
Re: default enconding
Tom Lane <tgl@sss.pgh.pa.us> writes:

> ... in other words, it doesn't require the double quotes.  I don't see
> the value of being more restrictive.  Why is this annoying?

Note also that using iso-8859-1 is not more restrictive, but just the
opposite. Using iso-8859-1 will be useful also for English users since
some words in use in the English language use characters not in the
ASCII encoding, resumé for instance.

Regards,
Manuel.

27 Mar 2004 19:50:45 -0600
Manuel Sugawara <masm@fciencias.unam.mx>
Re: default enconding
> 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. So what about changing the
> behaviour to either don't accept characters with the 8 bit set or
> accept by default strings in the iso-8859-1 encoding instead of ASCII
> endoding by default.

Apparently regarding everything ISO-8859-1 is not correct:-)

Probably we need to make quote_indet() a little bit smarter so that it
should quote input text only when it includes ASCII capital letters
and any other non delimter-appropreate letters except 8 bit
characters.

BTW, currently tab completion is not working for multibyte
encoding(including UTF-8, I guess) because it's broken in that it's
not multibyte ware.

I think we need to fix that as well.
--
Tatsuo Ishii

Sun, 28 Mar 2004 13:50:58 +0900 (JST)
Tatsuo Ishii <t-ishii@sra.co.jp>
Re: default enconding
Tatsuo Ishii <t-ishii@sra.co.jp> writes:

> I think we need to fix that as well.

I do agreee, however, we have to start somewhere.

Regards,
Manuel.

28 Mar 2004 00:13:46 -0600
Manuel Sugawara <masm@fciencias.unam.mx>
Re: default enconding