Assign select result to variable in Netezza stored procedure

Now THAT is a lengthy title for a blog post.

Am currently working on stored procedure to calculate Dijkstra's shortest path when I ran into this problem (as stated above).

Looked through Netezza's Stored Procedure guide but couldn't find anything of use (perhaps I was not looking hard enough.

Unfortunately for me even more when most of the SQL-variants out there also couldn't point me in the right direction (even PostgresSQL!)

I blame you for not being able to sleep tonight!

After examining the error code in Aginity multiple times, I tried to infer that the INTO probably had to be put after the statement, since the error message was complaining something about not being able to do select a variable before doing an INTO.

So what if the variable was put after the INTO?

Maybe even after the whole statement itself.


 DECLARE
vID varchar;
vESTIMATE integer;
...
...
select '5','8'--id , estimate,
from 
(
select row_number() over (order by estimate) row_num,id, estimate 
from SNA_TEMP_PATH
where done = 0
order by estimate
) A
 where A.row_num =1
into vID,vESTIMATE;

RAISE NOTICE 'vID now is %',vID;
RAISE NOTICE 'vESTIMATE now is %',vESTIMATE;

 And it worked. :)

Comments

Post a Comment

Popular posts from this blog

A Basic Recipe for Machine Learning

Image
Ever since wrapping up the three Deep Learning courses by Andrew Ng I've been meaning to write down some of the gems that he's highlighted throughout the course. One of the nice ones that I felt needed to be written down is his general recipe to approaching a deep learning algorithm/model. I've basically summarized it in a flowchart below (because everybody loves a flowchart right?) Basic deep learning recipe What is bias and variance? The below diagram is the typical explanation that I'm sure most of us are used to.  Graphical illustration of bias and variance How can we know if we have high bias or high variance?  For high bias, we could take a look at the training set performance. A poor performance is an indicator of a poor model fit, and signals that we could try to apply a bigger network to get a better fit of the model. For high variance, we could take a look at the validation set (or dev set - as Andrew calls it) performance. ...
Keep reading

HIVE: Both Left and Right Aliases Encountered in Join

Recently was stuck on this error while trying to do a JOIN in HIVE. Below is my SQL create table ma.internet_v2 as select A.msisdn, A.imsi, A.dt, A.start_time, A.end_time, A.url, A.ttl_connection_dur_ms, A.ttl_upload_bytes, A.ttl_download_bytes, A.ttl_cdr_cnt, coalesce(B.domain_desc,A.domain_desc) domain_desc, coalesce(B.subdomain_desc, A.subdomain_desc) subdomain_desc from db.internet A left outer join hfz_domain_name_mapping B on instr(A.url, B.url_pattern) > 0; HIVE then give me and error message "Both Left and Right Aliases Encountered in Join". After going through some mail threads it seems that HIVE can support certain types of join. Only equality joins, outer joins, and left semi joins are supported in Hive. Hive does not support join conditions that are not equality conditions as it is very difficult to express such conditions as a map/reduce job. A poster from  Stack Overflow  suggested that one should use WHERE instead of ON. Duly following his advice,...
Keep reading

MVNO: Through thick and thin

The below article was taken from Silicon.com. Click here to read the actual article. By Natasha Lomas, 27 October 2008 16:23 MVNO? That'll be an abbreviation - another pointless four letter one no doubt… Right and wrong. MVNO stands for mobile virtual network operator - and it refers to a rather intriguing slice of the mobile pie. I'm listening… Building and operating a mobile network is an expensive business, not least because it requires radio spectrum, so the number of mobile network operators (or MNOs) is limited to, at most, a handful per market. For instance, the UK market has five: 3, O2, Orange, T-Mobile and Vodafone. Spectrum does not come cheap. The auction for 3G licences in the UK - way back in 2000 - ended with five companies shelling out a whopping £22.47bn for the privilege of flogging third-generation services to Brits. So the requirement for large capital expenditure to set up a mobile network goes some way to explaining why actual networks are not 10-a-penny. ...
Keep reading