Hi,

While I think your heart is in the right place, I don't see this as very practical to implement for all database systems. The reason being is that some commercial DBMS vendors have literally thousands of possible errors with some being 'numbered' and others not. Also, depending on the version of the DBMS, a single error message might mean two completely different things.

If anyone was thinking of creating such a database of error messages, I would recommend to concentrate on the free and open source database systems first. Postgres, MySQL, SQL Lite, etc. If it becomes feasible, expanding it out to the commercial DBMS systems.

The real problem isn't so much the error messages but more of the context of the errors with respect to the application. I *do* like the idea though I suspect it would be better off explaning them at the application level instead. (duplicate key = dependents for Customer # 1883 already submitted. Would you like to resubmit them?)

Jason L. Froebe

Team Sybase member

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

In reply to Re: Mapping database errors to user errors by jfroebe
in thread Mapping database errors to user errors by jplindstrom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.