>> inserting nulls - or - empty strings? drunken dba's debate this for hours.
but since CF and java don't do nulls, you'd have to ask why bother? I mean, not writing code like this SET thisField = <cfif len(args.theValue) EQ 0 > NULL <cfelse> <cfqueryparam type="CF_SQL_CHAR" value="#args.theValue#" /> </cfif> , thatField = <cfif len(args.otherValue) EQ 0 > NULL <cfelse> <cfqueryparam type="CF_SQL_CHAR" value="#args.otherValue#" /> </cfif> has got to be a saving of 20% on data connection code compared to SET thisField = <cfqueryparam type="CF_SQL_CHAR" value="#args.theValue#" /> , thatField = <cfqueryparam type="CF_SQL_CHAR" value="#args.otherValue#" /> I just thought of another twist: you could tell the difference between uninitialised values (null) vs any field that's been processed at least once (empty string). "Empty String" could now mean "not known at this time" and "NULL" becomes "yet to be processed" any thoughts? cheers barry.b --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
