Hello all!
I know this question was asked formerly, but I could not reproduce a solution.
So let me ask again: Why does clover treat empty strings "" as null? Is this behavior configurable? I know from the database point of view it does not make sense to have empty strings. But in my case i run into problems with old data. I have to migrate data from oracle to postgres ( 8) and the application behind has a special semantic that relies on null (meaning that the value is not set) and empty strings (meaning the user wants to have an empty string).
Do you have suggestions.
cheers
Alex
I know this question was asked formerly, but I could not reproduce a solution.
So let me ask again: Why does clover treat empty strings "" as null? Is this behavior configurable? I know from the database point of view it does not make sense to have empty strings. But in my case i run into problems with old data. I have to migrate data from oracle to postgres ( 8) and the application behind has a special semantic that relies on null (meaning that the value is not set) and empty strings (meaning the user wants to have an empty string).
Do you have suggestions.
cheers
Alex
-
Hello,
you can't set on clover field string with length 0, but you can set blank string (" "). I hope it will help you. -
Since CloverETL version 2.9 , String field/variable distinguishes between NULL and empty string (zero length).
Please sign in to leave a comment.
Comments 2