X-Original-To: pgsql-bugs@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4BD8A476352; Thu, 3 Apr 2003 13:18:32 -0500 (EST) Received: from ossdev2.mcdean.com (suxmcdgw2.mcdean.com [63.89.89.108]) by postgresql.org (Postfix) with ESMTP id AC3DF476334; Thu, 3 Apr 2003 13:18:30 -0500 (EST) Received: from crystalballinc.com (localhost.localdomain [127.0.0.1]) by ossdev2.mcdean.com (8.11.6/8.11.6) with ESMTP id h33IRv715797; Thu, 3 Apr 2003 13:27:57 -0500 Message-ID: <3E8C7D2C.3060702@crystalballinc.com> Date: Thu, 03 Apr 2003 13:27:56 -0500 From: Darren Ferguson Reply-To: darren@crystalballinc.com Organization: Crystal Ball Inc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: muhammad umar Cc: pgsql-bugs@postgresql.org, pgsql-general@postgresql.org Subject: Re: [GENERAL] Suggestion References: <20030331105002.14648.qmail@web41110.mail.yahoo.com> In-Reply-To: <20030331105002.14648.qmail@web41110.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-35.6 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/44 X-Sequence-Number: 5817 The database parser in 7.3.2 tells you the character at which the error occurred. You could always upgrade to that version instead of bumping your gums on a topic where people spend there own free time providing a system for you to use. Have some consideration Darren 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 " ,,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 > >