Show description

Schema objects are, I believe, better capitalized. I would strongly advise against using a binary or case-sensitive collation for the database itself, since this will cause all sorts of unintended errors. A quirk of all European languages is that words mean the same thing, whether capital or lowercase letters are used. Uppercase, or majuscule, lettering was used exclusively by the Roman Empire, and lowercase, or minuscule, was developed later on, purely as a cursive script. The idea that the case of letters changed the meaning of words is a very recent novelty, of the Information Technology Age.

Because we've chosen YAML as our standard, purely because of its readability, we'll need to either convert it to XML with an existing utility such as YAXML, or knock something together to do the job. As YAXML is little more than an aspiration to write a utility, rather than a complete, tested solution, we'll choose the latter option. Besides, it is more fun, and easily altered for particular needs. More on YAML YAML, which is a superset of JSON, was first proposed by Clark Evans in 2001. " It is a means of serializing both objects and relational data in a way that is reasonably intuitive.

What the function does is unimportant; the point here is to observe the XMLDOCS header. <,') integer: 1 if whitespace, otherwise 0 **/ RETURNS INT 43 Chapter 2: Documenting your Database AS GO BEGIN RETURN CASE WHEN PATINDEX( '%[A-Za-z0-9-]%', @string COLLATE Latin1_General_CS_AI ) > 0 THEN 0 ELSE 1 END END Listing 2-2: A header in XMLDOCS format. Extracting the XML file from the comments isn't too hard and, once we've got it, we can put it into Sandcastle. What you want to aim for is as shown in Listing 2-3.