Problem with Column types and String

Question

Hi
I have some problem while comparing against empty string.
My column is of type it_Linked_Button. Actually it seems that column type doesn't matter.
If cell that belongs to this column is empty and based on other columns' values I put some value into this cell.
It works fine.
But when I clear that cell and try to put some value again nothing happens.
In my if statement I'm checking against empty string and it fails second time.
Before I put anything in that cell (in debugger) that value is "" so it is empty and it works.
(OK, I see that after I posted this message it was slightly reformated)
But after I put something and clear that cell and try to put something again (in debugger) I get "(here is some long space) " which fails String.IsNullOrEmpty(var) test.
What is going on? Has it something to do with Column type?
How to clear it so I can put something in it again?
One more thing - to put values and clear it I use DbDataSource SetValue method. And String.Empty or ""(doesn't matter)
Thanks
Kamil
NOTE
I made some workaround that gives me the behaviour I want but still I would like to know what is going on?
Edited by: Kamil Wydrzycki on Sep 24, 2009 12:57 PM

Answer 1

DrLaszloJamf wrote:
warnerja wrote:
DrLaszloJamf wrote:
1. Could you define an Enum? Then you could switch on enum values.
2. Wait for Java 7 which is supposed to extend switch to strings?3. Put the target strings in a collection, write a loop to find the match in the collection and use the matching index in the switch statement. At least that will get rid of the hashcode kludge, where it won't mistakenly 'match' a string which isn't the actual target.3b: Map<String, Command>Yep.
I also wanted to point this out to the OP:
For example, let's say the 7 character string "BugABoo" happens to have the same hashcode as "EDI_DOC". And let's say your input just happens to have the string "BugABoo" in it, where you're extracting the 7 character substring. See the problem? You're getting "BugABoo" but treating it as if it really were "EDI_DOC", by virtue of comparing hashcodes instead of actual strings.
OOPS!