Today was a sort of rough day at work. After having recently combined two databases into one, we noticed that a lot of things aren't...working correctly. Now, I received a message from one of the societies that we provide online access to. They provided me with a member's name and email address. I wasn't able to locate this information in our database, so I wrote back requesting her account number. She emailed me the member's account number. I looked that up in said disasterous database, and wasn't able to find that either. So I write back again, saying that we can't find the record. She emails my boss, telling her that the record IS coming to us, and copies and pastes the information exactly as it appears on the record that was sent to us. My boss enters the member's email address and IMMEDIATELY locates the record. And comes over to me to give the "you're incompetent" speech. Turns out that when they combined the databases, they didn't notice, or didn't CARE, that although one may double click in a field in the oracle form, and is given the message, "Field set to Case Insensitive Query", the case sensitivity status is not actually changing at all. So, when I entered namechanged@toprotecttheannoying.com, when the email was actually NAMECHANGED@TOPROTECTTHEANNOYING.COM, the record wasn't found. The same would have been true had I bothered to query by name, which I didn't, as queries on names generally take about 5-7 minutes since the combining of he databases. Now, you say, there's still the matter of the account number, right? Surely an account *NUMBER* wouldn't be affected by a case sensitivity issue, right? And you're absolutely right. Indeed, I would have been able to retrieve the record, had the account number been sent to me correctly. It was not. It was sent to me with an extra "0" in the middle. Now, when all was said and done, who got the lecture? Was it: a) the people who take care of the database, who didn't notice, or didn't inform us that although we were getting a message telling us that our queries were case insensitive, the weren't; or b) the person who gave me the incorrect account number? No. It was me. Because I a) shouldn't just "trust" that the case insensitive query was really case sensitive (damn me for being so trusting!); b) should have "played around with the account number a little", (realized there as an extra "0") before "bothering" the society. OOOOOOOOOOOOOOOOOOK. I guess it must be me. And, to top it all off, someone swiped my lunch from the fridge. Read the corresponding dream.