Is this Valid Oracle Stored procedure?

By the scope rules, it will use the column name before the parameter name, so that update isn't doing anything. I always stick "p_" before each parameter name to avoid conflicts like that.

Thanks man. Your answer will be my argument :) – ibmkhd Nov 7 '10 at 13:56 I've worked at places that also use some sort of prefix to indicate a variable or parameter. One of them used "IN_", "OUT_", and "INO_" to also indicate the direction of the parameter.

– OMG Ponies Nov 7 '10 at 19:59 1 "Best practice" according to Oracle is to always use aliases: e.g. UPDATE TRC_MESSAGES_REMINDERS t SET t. Msg_status = SAM2_update_message_status. Msg_status WHERE t.

MSG_ID = SAM2_update_message_status. Msg_id – Jeffrey Kemp Nov 8 '10 at 1:00.

But I don't know if it's the same in oracle. I called it but no errors and the values I sent not reflected on the table. Is this a Valid procedure?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions