Well let's say there are 2 programmers...

1 makes the select box and fills all the values in in lower case

The second programmer is doing whatever based on the value selected in the select box and writes this line:
<cfif FORM.MySelectBox eq "BIFF">

That condition will never be true because case was not considered...the line should read

<cfif UCase(FORM.MySelectBox) eq "BIFF">

This is assuming that "biff" only has one meaning no matter what case it's in.

Does that make sense??

Bryan Stevenson B.Comm.
VP & Director of E-Commerce Development
Electric Edge Systems Group Inc.
t. 250.920.8830
e. [EMAIL PROTECTED]

---------------------------------------------------------
Macromedia Associate Partner
www.macromedia.com
---------------------------------------------------------
Vancouver Island ColdFusion Users Group
Founder & Director
www.cfug-vancouverisland.com
  ----- Original Message -----
  From: Bryan F. Hogan
  To: CF-Talk
  Sent: Monday, March 01, 2004 12:46 PM
  Subject: Re: populating dropdowns

  Why would checking case insensative get you into trouble?

  As you say it would be bad design to make HIGH and high mean differant
  things, so why then would session.username='high' mean anything
  differant than UCASE(session.username) is 'HIGH'?

  Bryan Stevenson wrote:

  > The value could be  high,High,HIGH,HiGH etc. SO checking to see if
  > it's  'high' can get you into trouble (unless of course HIGH and high
  > have different meanings...then by all means it should be as it was
  > written (but IMHO that would be bad design to have HIGH and high mean
  > different things).
  >
  > It's case sensitive because the value of username could be stored in the
  > DB as all upper/lower/mixed case....to be case insensitive you have to
  > check values of the same case...all upper...all lower...whatever floats
  > yer boat.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to