The purpose of getting the data in the first place is to allow my boss to see that people are still not doing things they are supposed to. He can then send out reminders so we can establish better habits. My plan is to replace the null value with a description making it obvious that the value had not been set instead of just leaving a big ugly blank spot.
Keep up with my goings on at http://theillien.blogspot.com Chas Owens wrote: > On 6/14/07, Mathew Snyder <[EMAIL PROTECTED]> wrote: >> I'm building a hash using values from a database backend to an >> application we >> use in house. The application has a field which contains a customer >> name. This >> values is supposed to be set by the person handling the work but >> sometimes >> doesn't get done. This leaves a NULL value in the database which, in >> turn, >> leaves me with a null key in my hash. >> >> I've tried resetting it by assigning the value to another key so I can >> delete >> the element but so far nothing has worked. I've tried to access it with >> $hash{}, $hash{""}, and $hash{''}. None of these will allow me to >> access the data. >> >> I could probably reassign it through more complicated means but that >> would >> require creating objects and accessing methods I'm not familiar with. >> If anyone >> knows an easier way to access a null key I'd appreciate hearing it. >> >> Thanks >> Mathew >> -- >> Keep up with me and what I'm up to: http://theillien.blogspot.com > > Jenda's solution should work, but if you are just going to throw it > away (instead of logging it as a problem) then why fetch it from the > database in the first place? Add "customer_name is not null" to the > where clause. Fetching data you are not going to use is unkind to the > database, the network, and your program. > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
