> It's null. OpenBD (and BD before it) has had null for quite a while, so the > variable remains defined with a value of null as opposed to nuking variables > when they're null as CF does (which has never made sense to me).
Fair enough. Personally I agree... CF's thing with not having nulls and using empty strings instead was just a crap idea from the outset. However BD not following that lead... also not great, I think. CF has set the precedent - optimally or otherwise - that nulls returned from the DB are exposed to CFML as empty strings. And BD should have followed suit there, I reckon. However we are where we are, so that can't be helped now. Railo, FWIW, returns empty strings like CF does. Anyway, no probs. I see what you've done and why, so fair enough. Cheers for the quick feedback! -- Adam -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
