> Hrmmm...one thing to note with any of this is that by 'hardcoding'
> in the errormsg itself, it makes it difficult to 'internationalize' a
> program...in that I can't run a single server on my machine that can
> easily deal with a 'French' customer vs an 'English' one, vs a 'Japanese'
> one...I'd have to recompile for each.
Oops, postmaster can't access any database tables, so each backend
would have to load it. I would recommend dumping the default out with
COPY as part of initdb, let the postmaster load that file, and backends
can load their own. In fact, we may just keep them as COPY files, so
they can be easily edited and loaded/unloaded.
>
> Vadim's other point, about putting this in the front end vs the
> backend, I think, is more appropriate, that way it is application specific
> vs server...
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.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)