> Creating central message files/objects has the added advantage of a much
> simpler locale support - they're just resource files, and they're NOT
> embedded throughout the code.
> Finally, if you do want to have some kind of error classification beyond
> the SQL code, it could be encoded in the error message file.
We could also (automatically) build a DBMS reference table *from* this
message file (or files), which would allow lookup of messages from codes
for applications which are not "message-aware".
Not a requirement, and it does not meet all needs (e.g. you would have
to be connected to get the messages in that case) but it would be
helpful for some use cases...
- Thomas
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
- [HACKERS] More on elog and error codes Peter Eisentraut
- Re: [HACKERS] More on elog and error codes Philip Warner
- Re: [HACKERS] More on elog and error codes Tom Lane
- Re: [HACKERS] More on elog and error codes Peter Eisentraut
- Re: [HACKERS] More on elog and error code... Philip Warner
- Re: [HACKERS] More on elog and error ... Philip Warner
- [HACKERS] Re: More on elog and error ... Thomas Lockhart
- [HACKERS] Re: More on elog and e... Philip Warner
- Re: [HACKERS] More on elog and error ... Peter Eisentraut
- Re: [HACKERS] More on elog and e... Philip Warner
- Re: [HACKERS] More on elog a... Tom Lane
- Re: [HACKERS] More on el... Philip Warner
- Re: [HACKERS] More on el... Tom Lane
- Re: [HACKERS] More on el... Philip Warner
- [HACKERS] Re: More on elog and error codes Thomas Lockhart
- [HACKERS] Re: More on elog and error codes Gunnar R|nning
- Re: [HACKERS] More on elog and error codes Christopher Sawtell
