RE: Patch for Improved Syntax Error Reporting
От | Dave Page |
---|---|
Тема | RE: Patch for Improved Syntax Error Reporting |
Дата | |
Msg-id | 8568FC767B4AD311AC33006097BCD3D61A2D6E@woody.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Patch for Improved Syntax Error Reporting (Neil Padgett <npadgett@redhat.com>) |
Список | pgsql-patches |
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 02 August 2001 22:16 > To: Dave Page > Cc: 'Bruce Momjian'; Neil Padgett; pgsql-patches@postgresql.org > Subject: Re: [PATCHES] Patch for Improved Syntax Error Reporting > > > Dave Page <dpage@vale-housing.co.uk> writes: > > In the case of pgAdmin, it displays the error messages as > returned by > > the backend. I have no desire to start maintaining my own list of > > error codes/messages, especially as those returned by the > backend are > > generally user friendly, and I certainly don't want to > start parsing > > user supplied SQL statements myself - I'd rather leave that to the > > real parser. > > Maybe I'm confused, but I don't think any of the proposals > would require you to do any of those things. The only case > that requires any significant new effort from the client app > is where it reformats queries before sending them on to the > parser ... but that is knowledge you've already built into > the client, no? You just have to remember what you did so > that you can map a backend error index into the original text. Like I said in another message, I seem to only have received bits of this thread - I've probably misunderstood the comments that I read before writing that.... it's been a long day and it's 11PM here now! Regards, Dave.
В списке pgsql-patches по дате отправления: