| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | scan.l: check_escape_warning() |
| Date: | 2008-01-11 15:16:12 |
| Message-ID: | 20080111151612.GA18802@feivel.credativ.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
could anyone please enlighten me whether this function is still needed?
AFAICT check_escape_warning() only has significant action if
warn_on_first_escape is true. This variable is set to true only on label
xqstart, but to false on xestart. However, check_escape_warning() and
check_string_escape_warning() btw. are only called in mode xe. Seems to
me that both are never called, or what am I missing?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberts, Jon | 2008-01-11 15:32:05 | could not open relation: Invalid argument |
| Previous Message | Richard Huxton | 2008-01-11 13:26:13 | Re: Storage Model for Partitioning |