public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dennis Gearon <[email protected]>
To: [email protected]
Cc: muhammad umar <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [GENERAL] Suggestion
Date: Thu, 03 Apr 2003 11:16:55 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

I stand corrected, after reading tom's post about 7.3.2.

Error reporting to the point of failure in the querry is COOL, thanks to all who 
worked on that. I will have to bug my provider to install the latest version.

Dennis Gearon wrote:
> 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 [email protected] so that your
>> message can get through to the mailing list cleanly
>>
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/docs/faqs/FAQ.html
> 

view thread (6+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [GENERAL] Suggestion
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox