In the client you are not giving the field a value so it is going in to
the db as NULL.  
 
In XML you are specifying the element so by definition you are saying a
value exists for the field (it just happens to be empty). When the
element does not exist in the XML it is being saved as NULL to the db.
In your XML definition does that element have the nillable attribute?
 
Fred

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ganga Prasad
Sent: Friday, April 11, 2008 8:17 AM
To: [email protected]
Subject: Re: Difference between NULL and ""


** Thanks Fred
It should behave equally in the native application in Remedy and the
external interface. As it can be seen before I start "My Approch"  the
system was behaving differently for the native and external application.
Not able to get here ?? :(

-- 
Thanks and Regards,
Ganga Prasad Pattnaik,
( Remedy Skilled Professional )
-------------------------------------------------


On Fri, Apr 11, 2008 at 6:40 PM, Grooms, Frederick W
<[EMAIL PROTECTED]> wrote:


        ** 
        Null is defined by the ISO SQL standard as different from both
an empty string or the numerical value 0.  Null indicates the absence of
any value, the empty string and numerical zero both represent actual
values.
         
        From:   http://en.wikipedia.org/wiki/Null_(SQL
<http://en.wikipedia.org/wiki/Null_%28SQL> )
         
        Fred

________________________________

        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ganga Prasad
        Sent: Friday, April 11, 2008 7:40 AM
        To: [email protected]
        Subject: Difference between NULL and ""
        
        
        Hi all
        
        Is there any difference between NULL and "" in a character field
??
        My Scenario
        I have a character field. The value to the character field is
supposed to come from a already existing backend from.
        My Requirement.
        On saving I should not be able to save any value in the
character field other than whatever record is present in the BACKEND
Form
        My Solution
        I wrote a filter (RUNIF : character field != NULL) which will go
for a SQL. The SQL will find out the present value in the ticket with
the BACKEND record. Once it is finding, it will make a flag field with
count of records found (Usually 1). If no backend records found then it
will make the flag 0( zero matching records)
        The very next filter will check for the value in the Flag field;
If it is 0 then give a error message
        My problem
        It is working as expected as long as I am opening my Remedy
client and save the ticket.
        But when I am trying to create a ticket in my application
through another application by XML without passing the value to the
character field it is throwing an error to the originating system.One
strange thing is that if in the xml if i am removing the
<characterfield> completly; it is working fine.
        My Approach
        I approached with hit and trial method that before going for SQL
I set the character field NULL if it is "". Now it is working fine.
        My Doubt
        Is this the way remedy should behave ?? is there any diff
between NULL and "" ??
        My Setup
        ARS V 7.0.01 P003
        No ITSM
        Completely Customized appl.
        
        -- 
        Thanks and Regards,
        Ganga Prasad Pattnaik,
        ( Remedy Skilled Professional )
        -------------------------------------------------  
        
        __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the
Answers Are" html___ 





__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to