Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I think we need to fix that as well.
I do agreee, however, we have to start somewhere.
Regards,
Manuel.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> 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
Tom Lane <[EMAIL PROTECTED]> writes:
> Manuel Sugawara <[EMAIL PROTECTED]> 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
Tom Lane <[EMAIL PROTECTED]> 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 Engl
Manuel Sugawara <[EMAIL PROTECTED]> 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 th
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 t
