Yaarrrrrrrgggg.. work correspondence

I be celebrating the holiday like an admiral.. here is an email I sent
out to me deckhands (it be about two score of them) 1/2 of which I do
not know... yarrrrggggg be a pirate biatch!

Yarg... Let me be clarifying a little bit: This field be renamed last
January for greater consistency within the system (elements that return
the same data should be named similarly, no?). Whenever our crew be
making changes as such the old field is "aliased" so previously written
queries wont be crashing upon deadman's reef.
In our release this weekend a folder was moved and the aliases were lost
in the transition. This be not intended and will be remedied.
The fix be as Captn R say but you really shouldn't be waiting for the
alias to be brought in. The query should be rewritten using the most
current name of the column. Because the name change went in last
January we didn't have release notes so no one knew it changed. In the
future when release notes come out stating a renaming of a column
(should be VERY rare.. like the flesh-eating red whale) ye should edit
yer queries to use the new name...
YAAAAAARRRRRRRRGGGGG
--admiral m