maybe he's a little vitrolic, but the error reporting could be MUCH better.
Seems like the parse tree should be able to show where the error is.
muhammad umar wrote:
> hello,
> im using PostgreSQL 7.3.1 on i686-pc-linux-gnu,
> compiled by GCC 2.96.
> i have a suggestion for the name of this DBMS, and
> that it should not be PostgreSQL but it should be
> PregreSQL, as im feeling its a DBMS that perhaps might
> be used 100 years ago,,proof for this is its
> techniques for showing errors that if we have a 1400
> lines sql query contain some error,,it give error as "
> parse error at or near <some column name>" ,,now if
> that column is used at several places ,,we might have
> to browse the whole of the cream.......
> this is one of example of the limit of stupidity this
> DBMS having,,,
> this used to waste the time that should be spent in
> development...so consider changing the name of this
> stupid DBMS,,
>
> regards
> Muhammad Umar Liaquat
> Database Administrator
> Vigilant Systems Limited.
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
