Re: One True i18n Table

>> The above requires a structure change to add a language. <<

I knew I'd catch "1NF" Hell for that, but I will defend it by saying:

1. This is an auxiliary table, not part of the schema proper. Do you bitch that Star schemas are not normalized?
2. You can easily define VIEWs on it for your target language.
3. This inherently forces you to have all the languages for each SQLSTATE code, while a 1NF table does not. This is the real reason for violation of 1NF.
4. You don't invent or add languages very often. Tho I do know of one product that was adding Klingon to its error messages. Seriously; it was for a demo at a trade show to show off the internationalization features. ("Unknown error = Die in ignorance!!", sort of a user surly interface instead of user friendly).