| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| NULL STRING WHEN SELECTING FIELDS INTO XML |
« View previous topic :: View next topic » |
| Author |
Message
|
| MikeTamari |
 Posted: Sun Apr 06, 2003 5:36 am Post subject: NULL STRING WHEN SELECTING FIELDS INTO XML |
 |
|
Apprentice
Joined: 04 Feb 2002
Posts: 26
|
Whenever I select rows into the OutputRoot XML and one of the fields has a null value, it is transferred to the OutputRoot XML as the string 'NULL', this is bad news for me since it eventually goes into another DB.
Replacing the string is not good enough since technically someone can actually put the string 'NULL' in the table as a legitimate string.
I tried selecting with nullif, it works, but the select becomes extremely slow, (there are about 20 fields selected).
Any other ideas, I am starting to run out of them,
thanks. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Apr 06, 2003 9:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you put the results of your select into the environment, they will stay as NULL values, rather than 'NULL' character strings.
So instead of saying
set OutputRoot.XML.myDoc.myResult[] = ...
you would say for instance
set Environment.Variables.myResult[] = ... |
|
| Back to top |
|
|
| MikeTamari |
| Posted: Sun Apr 06, 2003 10:39 pm Post subject: |
|
|
Apprentice
Joined: 04 Feb 2002
Posts: 26
|
Thanks, if I use the Environment variables all the way including the DB node it works just great.
Does using the Environment variables have any problems/limitations and or advantages ?
We have always used the OutputRoot.XML to flow between nodes. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
