200 is such a hard number to work with, after all

Will in #wilug shared this fun Microsoft bug. From the report:This problem occurs if the fully qualified domain name ( FQDN) of your computer is exactly 200 bytes long. During logon, one character more than the 200-byte allocation is written and heap corruption occurs.Of course, the suggested workaround is just... [Read More]
Tags: microsoft

Using NOT LNNVL() is NOT GOOD()

In re-working some old reports that I'm still maintaining, I decided to clean up instances of "WHERE foo > bar or foo is null" with some LNNVL() loving. Given the nature of my query and of LNNVL(), I plugged in LNNVL(foo > bar) and prefaced it with a NOT, since... [Read More]
Tags: bugs oracle lnnvl

IT'S THE JOIN[T]!

See what I did there? 5 points to anyone who can name the reference. 10 points if you can name the original reference that I wasn't even thinking of. Void where prohibited.Sachin, broadcasting live from his blog Oracle Online Help, has posted a nice primer on the differences between three... [Read More]
Tags: oracle joins