This article is bound to be controversial, but I beg you to keep an open mind as you read. I have put a lot of research into this, it is not your standard knee jerk "OOP Sucks" article. In fact, you will find in the end that I will recommend still learning Object Oriented Programming (OOP), if you haven't already.
I just spent the last couple of hours trying to figure out why some of the PDFs on a page are coming back as corrupted, while the rest work fine. Turns out it was that BLOB setting in the datasource! I didn't create this datasource, but when I checked it, sure enough BLOBs were not enabled for this datasource. Once I turned that setting on, my PDFs started working fine. However, I don't know why some of them would work, even though that setting was off...
And before you yell at me for using BLOBs...I am not the one that originally wrote this app, and pulling all of these PDFs out of the DB so I could store them on the file system is not a project I want to undertake right now, so I'm just living with the BLOBs for the time being.
So if you are fighting with corrupted PDFs, check your data source setting. :)
Ok, I know that ColdFusion makes database work a piece of cake, but calling CF a database is going too far. But I just ran across this site while searching the web that does just that:
"Will ezDatabase work with other databases (MS SQL, Coldfusion, Oracle)?"
Too funny! :)
Yesterday I found out there's a DateDiff function in SQL Server that works the same as ColdFusion's DateDiff. Today I was curious if DateDiff is part of the ANSI SQL standard, or if it's a proprietary Microsoft SQL extension. I never found my answer, but it doesn't look like Oracle supports it. However, I did find some interesting facts about SQL:
I was reading The Daily WTF today and saw what you may need to do if you want to access a Sybase database from MS Access. My first response was, why are you using Access? Ok, I know that a lot of people have legacy code and/or users out there. But this person was getting a useless error message in Access, and had found help on Sybase's site. He had to use the registry editor to create a datasource with this string "WorkArounds2=8192" So obviously, the Access developers had found this problem in development (probably QA actually), but rather than fixing it they created this 'workaround'.
By the way, how many of you knew that Sybase SQL Server is the codebase that Microsoft started with to build MS SQL Server? Another interesting historical note, the first release of MS SQL Server was 1.0 for OS/2 in 1989 (no Windows release). Also, there was no MS SQL Server 2.0 nor 3.0. They skipped from 1.0 to 4.21 for Windows NT and OS/2 in 1993 (what the crap?) They then skipped v. 5 and realeased 6.0 in 1995. Can you say inferiority complex?