Any concerns with using NUL char with PowerHouse
Darren Reely
darren.reely@latticesemi.com
Fri, 18 Jan 2002 11:17:36 -0800
Blue,
Richard isn't talking NULL. He is talking about ascii value zero, NUL.
Being an ascii character, it should take up space in a database if the
database doesn't object. Surprisingly, quiz prints an empty string for it,
and it can be used in concatenation without the side effect of creating a
NULL string.
I'm still trying to understand what he really wants to do with it.
;On Sun Solaris
define my_nul_num INT*3 UNS SIZE 1 = 0
define my_nul CHAR*1 = CHAR(my_nul_num)
define my_NULL char*1 = NULL
define result_is_null char*20 = 'mystring' + my_NULL
define result_is_mystring char*20 = 'my' + my_nul + 'string'
Darren
"Edis, Bob" wrote:
>
> G'day Richard
>
> I've had problems in the past where an index used from primary file
> retrieval in a screen contained a null. The results were unpredictable
but
> often records could not be viewed even though a user had just entered
them.
> These were NOT the records that contained the NULL. Removing the NULLs
from
> the index column eliminated the problem.
>
> Regards,
> Blue
>