Hello,
for thanks for the great stuff you wrote.
I remember some time ago talk about error numbers in PostgreSQL. Are
they implemented? And standard SQL error codes (5 character long
strings). As PostgreSQL is moving towards ANSI SQL rather fast, it
would be nice to see standard error codes and messages as well.
> > > > I just think the WARN word coming up on users terminals is odd. I can
> > > > make the change in all the source files easily if we decide what the new
> > > > error word should be. Error? Failure?
> > > >
> > >
> > > Yes, that's one of the things I don't understand with PostgreSQL.
> > > ERROR would be much better.
> >
> > How about ABORT ?
>
> Sounds maybe a little too serious. We currently use WARN a lot to
> indicate errors in the supplied SQL statement. Perhaps we need to make
> the parser elog's ERROR, and the non-parser WARN's ABORT? Is that good?
> When can I make the change? I don't want to mess up people's current work.
Me too :-)
Ciao
Ciao
Das Boersenspielteam.
---------------------------------------------------------------------------
http://www.boersenspiel.de
Das Boersenspiel im Internet
*Realitaetsnah* *Kostenlos* *Ueber 6000 Spieler*
---------------------------------------------------------------------------