From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Jonathan Bartlett <johnnyb6(at)SDF(dot)lonestar(dot)org>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: syntax warning on |
Date: | 2001-05-18 15:57:08 |
Message-ID: | 3B054654.479AF356@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> Your patch has been added to the PostgreSQL unapplied patches list at:
> http://candle.pha.pa.us/cgi-bin/pgpatches
> I will try to apply it withing the next 48 hours.
> > I'm just starting to look around the postgres source code. Anyway, I saw
> > a few lines about syntax warnings in psql that were ifdefed out because
> > they were too annoying. This patch puts it back in, but only gives the
> > error once per session.
Uh, the warnings were commented out *because they were too annoying*,
but were left in as a placeholder for doing something different later.
I'm not sure that the "something different" should be "annoying only
sometimes" ;)
I'd suggest that this patch not be applied at least until we reopen the
discussion and conclude that raising the annoyance level is A Good
Thing. The last time we had concluded that the role of the backend was
not to teach "proper SQL" but to Just Do It.
Complaining once per session does not give the predictable behavior I
would want.
Comments?
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-05-18 15:58:28 | Re: syntax warning on |
Previous Message | Fernando Cabrera | 2001-05-18 15:25:35 |