My guess is that your datetime got converted to a date before the comparison was done. There was likely an exact match after type conversion took place.

Yeah, I think you're right. Looks like SQL Developer truncating to just the date. The thing is it didn't feel like I was "making anything up" at the time because I knew the data had the date and time and my query was working in one place but not the other. I was incorrectly assuming SQL Develper was just truncating the results for display purposes. Time to track that setting down in SQL Developer.

I still don't see how telling someone they are just making stuff up can be considered anything but rude. I appreciate the help, but next time please try leaving the extra "commentary" at home.