Interesting question. Interesting in that it made me realize that I
have never had a need to do this. I think that any time I am allowing
nulls in string fields the app doesn't really care whether they're
specifically nulls or not. So I just accept the default of and it
hasn't caused any
I should add that I'm concious of legit data being confused for the
sentinal values, but I recognise Hal Helms collection (via Nando) of
pipe symbols, underscores and a backslash is pretty unique.
hmmm... perhaps I can get away with using some of the less common
ASCII chars - ones not readily
As I know him, Hal seems to think things through very thoroughly, and
he came to the conclusion that in CF, you need a string to represent
null. I think what he came up with is good enough for our purposes,
unless the field is named Keyboard Graffiti or something like that
and your application is
I've used NULL in the past, and it has worked well for me.
Or use a UUID... not much chance of people picking that.
Mark
On Thu, Feb 12, 2009 at 8:51 AM, Nando d.na...@gmail.com wrote:
As I know him, Hal seems to think things through very thoroughly, and
he came to the conclusion that in
