> Please find attached a patch to fix the "CREATE FUNCTION"  syntax error
> position bug I reported a few days ago.

This strikes me as much too intrusive to be worthwhile ... the problem
is simply not important enough to justify a protocol change.  Moreover,
I don't like the proposed protocol change anyway.  This approach only
solves the problem for psql-like error reporting, namely clients that
are going to regurgitate a string in their error message and aren't
very picky about whether that string really matches the original input.
One of the design goals for the error reporting feature is that GUI-type
clients should be able to mark syntax error positions by highlighting in
the original input window.  This proposal abandons that goal.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to [EMAIL PROTECTED] so that your
      message can get through to the mailing list cleanly

Reply via email to