From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | psqlhack(at)retep(dot)org(dot)uk (Peter T Mount) |
Cc: | vadim(at)krs(dot)ru, peter(at)maidstone(dot)gov(dot)uk, sferac(at)bo(dot)nettuno(dot)it, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] RE: [HACKERS] error messages not only English |
Date: | 1998-05-26 18:18:14 |
Message-ID: | 199805261818.OAA15206@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
>
> Why into C variables? You could have a function that returns the correct
> string for the error code, and have it default if it can't access the
> table.
So we run an internal SQL query to get the error message from a table?
I guess we could do it, but the system state while in elog() is only
partial. You would have to do the longjump, reset, then ru the query.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter T Mount | 1998-05-26 20:12:09 | Re: [GENERAL] RE: [HACKERS] error messages not only English |
Previous Message | Peter T Mount | 1998-05-26 18:07:35 | Re: [GENERAL] RE: [HACKERS] error messages not only English |
From | Date | Subject | |
---|---|---|---|
Next Message | David Hartwig | 1998-05-26 18:44:04 | Re: [HACKERS] Current sources? |
Previous Message | Vadim Mikheev | 1998-05-26 18:16:24 | [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE] |