Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at myibi@ibi.com and provide your corporate email address, company, and name.


Connect to myibi
Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Handling potential nulls in stored procedure calls

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Handling potential nulls in stored procedure calls
 Login/Join
 
Silver Member
posted
Good Afternoon,

I am calling a stored procedure like so:

ENGINE SQLMSS SET DEFAULT_CONNECTION CONN_DEV
SQL SQLMSS
EX getPermissions '&&USER_ID', &&TEST_VAR;
TABLE FILE SQLOUT
PRINT *
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE SET ASNAMES ON
ON TABLE NOTOTAL
ON TABLE HOLD AS 'foccache/hold_test' FORMAT ALPHA
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE OFF
END

TEST_VAR can potentially hold a guid or be null. If I'm understanding this correctly if it's null I have to pass the variable without quotes whereas if it's a guid I have to include the quotes. What is the easiest way to do make this work? My naive approach without knowledge of cleaner syntax would be:

if TEST_VAR EQ null
- run block without quotes
ELSE
- run block with quotes

But this is a contrived example, the actual use case involves 6 more parameters that I'm passing, most of which follow this guid or null scenario. So that solution wouldn't really hold up.

Thoughts on how I can do this? I'm assuming I'm just unaware of the proper syntax.

Thanks!

This message has been edited. Last edited by: FP Mod Chuck,


Windows 8203 All output formats
 
Posts: 47 | Registered: November 30, 2018Report This Post
Expert
posted Hide Post
Assuming you are getting null passed through, a small bit of DM will fix this.

-SET &MyTestVar = IF &&TEST_VAR EQ 'null' THEN &&TEST_VAR ELSE '''' | &&TEST_VAR | '''' ;

ENGINE SQLMSS SET DEFAULT_CONNECTION CONN_DEV
SQL SQLMSS
EX getPermissions '&&USER_ID', &MyTestVar;
TABLE FILE SQLOUT


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6349 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
Silver Member
posted Hide Post
Worked like a charm, thanks Waz!


Windows 8203 All output formats
 
Posts: 47 | Registered: November 30, 2018Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Handling potential nulls in stored procedure calls

Copyright © 1996-2020 Information Builders