Clean Clobbing

Greetings ladies and gentlemen, developers, testers, and project managers all across the digital plane, it is I, your highly trained blogcast specialist, wishing you a good day on this, the EIP web-ring, and welcoming you to Programming Excellence straight ahead.

Recall in passing that many moons ago, I mentioned that the CUD of CRUD at my place of business is done through the use of Character Large Objects and so-called Modification Requests.

The premise of this post is that you have to accept the fact that it is done this way and as bizarre as it is, that is how it is done and we can’t change it. Given that we can’t change how the database guys work, we can change how we work with what they give us.

Look out behind you, lady, it’s the Blob!

I was going to write about our second requirements session for the Carbon Copy Whiteboard. But I wanted to do something a little less structured. Requirements aren’t that important anyway. </sarcasm>

I’ll note that I write this post at a time when I really just don’t feel like writing a post. But I’m sticking with my Atwood blog diet of posting even if you don’t have anything to say or don’t feel like it.

Anyway, the Blob is better known as the Binary Large OBject. Its use is obvious: storing images, movies, PDFs, or any other kind of binary data. But of what possible use can CLOBs be? A CLOB is a Character Large OBject.